info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Locks, pls help


From: David Everly
Subject: Re: Locks, pls help
Date: Tue, 2 Oct 2001 12:31:26 -0600
User-agent: Mutt/1.2.5i

If I understand what you are trying to do, prehaps this will answer:

http://www.cvshome.org/docs/manual/cvs_18.html#SEC171

On Tue, Oct 02, 2001 at 07:11:06PM +0200, raptor wrote:
> hi,
> 
> I'm tring a loginfo-script.. and I got lock problems..
> OK first I expected that 'cause the cvs-commit is already finished at
> log-info-stage all locks should be already released so I can switch to my
> working directory and update it (read) .... but I have zero success and had
> to go to Repository to remove locks manually...
> I've read in the manual but the explanation of the LOCKS is too 'blury' ..
> First of all I have to create #cvs.lock dir, but how can I create such dir
> if I don't know where exactly (in which cvs-reposiroty dir) I have to create
> this one (i don't need it anyway)... I'm just chdir-ing to one of the
> working-copies (not the one that commits at the moment) and then tring "cvs
> update" ...
> Is there any way to tell previous/parent(maybe) process to release his lock
> so I can freely do my job.... Anyway, I'm not tring to change repository or
> work directly with it, so I don't need to request read-locks ...
> 
> And yes I read -central up-to-date files- thread and the solution with cron
> script... The problem is that this doesn't work for me... I and other
> developers can't wait 15 min to see their changes, they have to see their
> changes almost at the time after they commited their file .... And the times
> when I will have two developers commiting simultaneously are very, very
> rare..
> 
> SO THE MAIN PROBLEM STAYS : HOW CAN I TELL THE PROCESS THAT STARTED LOG-INFO
> SCRIPT TO RELEASE HIS LOCKS, SO LOG-INFO CAN DO HIS JOB .... (again mine
> script don't work directly with the repository files so it can't broke
> repository internal data, it just do "cvs update").
> One more thing at the time the log-info script is executed everything is
> commited successfuly so I don't see a reason for it to hold this lock..
> 
> Thanx alot for your pation reading this and for the answers of-course :"))
> =====
> iVAN
> address@hidden
> =====
> PS. I'm new to CVS and hope I'm not missing something obvious, but I think
> not :")
> 
> 
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs

-- 
address@hidden
V-Net:       622-3286
Phone: 1-719-535-3286
Pager: 1-800-724-3624 # 140-1311



reply via email to

[Prev in Thread] Current Thread [Next in Thread]