[Top][All Lists]

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

Re: strange line in CVSROOT/commitlog

From: Shubhabrata Sengupta
Subject: Re: strange line in CVSROOT/commitlog
Date: Thu, 7 Jun 2001 08:27:59 +0530

The locks are still being made in /tmp/cvslock - /tmp/cvs-serv15476
directory is not made for creating locks - CVS creates the directory and
puts the yet to be checked in copy of the file in there so that it can run
the commitinfo script on it. Only if the commitinfo script returns 0 does it
go ahead and modify the corresponding ,v file, Even here it makes a copy of
the ,v file before it modifies it. Normally you don't point the LockDir
variable to anything then the locks would be created in the directory in the
repository where you are checking in files to.

To see the contents of the /tmp/cvs-<pid of cvs process> directory - write a
commitinfo script and put a sleep in it.



-----Original Message-----
From: Paul MacAdam <address@hidden>
To: address@hidden <address@hidden>
Date: Thursday, June 07, 2001 4:07 AM
Subject: strange line in CVSROOT/commitlog

>Kind of a follow-up to previous question.
>(BTW, $USER and $CVSROOT in loginfo worked great!).
>In CVSROOT/config, I have LockDir set to: /tmp/cvslock
>The directory is drwxrwxr-x 4 cvs cvs
>In CVSROOT/loginfo, I have the following line:
>  ALL (echo ""; echo $USER; date; echo %{sVv}; cat) >>
>What's strange is the entry in CVSROOT/commitlog:
>Wed Jun  6 14:55:29 PDT 2001
>CVSROOT loginfo,1.6,1.7
>Update of /cvs-root/CVSROOT
>In directory
>Modified Files:
> loginfo
>Log Message:
> added echo before USER to record username in commitlog
>I would have expected the line "In directory
>to instead read "In directory"
>... or something like that.
>Does it look right to you? Maybe more generally, do you recommend the
>use of LockDir?
>Info-cvs mailing list

reply via email to

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