[Top][All Lists]

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

Re: Locks, pls help

From: Tobias Brox
Subject: Re: Locks, pls help
Date: Wed, 3 Oct 2001 00:47:06 +0400
User-agent: Mutt/1.0.1i

[raptor - Tue at 07:11:06PM +0200]
> hi,
> I'm tring a loginfo-script.. and I got lock problems..

Been there, done that.  It seems like the commit-lock is removed only after
the loginfo-script has returned.  It doesn't make sense to me?  I simply
forked the loginfo-script, and there were no problems at all ... 'xcept some
microseconds of extra delay, maybe :-)

To do a fork in perl, you might simply:

    exit unless fork;

> 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 wouldn't mess with it, I'd rather chose the solution above.

> 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

The longer the wait-time is, the more inefficient the working will be.  At
my former work-place both our development server and production server was
updated only some 12 times during each working day, and the developers had
no way to force through even an emergency 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..

Neither do I ... though there might be a reason.

> PS. I'm new to CVS and hope I'm not missing something obvious, but I think
> not :")

I think you're analyzing the problem right and beeing annoyed for the right
reason, but I think you're trying to solve the problem the wrong way :-)

Unemployed hacker
Will program for food!

reply via email to

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