[Top][All Lists]

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

Re: problem with lock file when committing file

From: Todd Denniston
Subject: Re: problem with lock file when committing file
Date: Tue, 02 Aug 2005 09:12:28 -0500

Julian Opificius wrote:
> No, my primary heartache is the intended location of the lock file in
> the message, which is not where my configuration keeps lock files - I
> use /var/lock for that so I can use pserver to prevent unlogged write
> access to the repository.
> Julian.
> ====================
> >
> > On 01/08/05, Julian Opificius <address@hidden> wrote:
> >
> >>6. I try to to check in changed file, and get ...
> >>cvs [commit aborted]: could not open lock file
> >>"`/usr/local/cvsroot/JPL069/PL069/FPGA/PL069_V01/,arinc_interface.vhd,':
> >>Permission denied"
> >>Which is a real problem, because I have CVS server configured to put log
> >>files in /var/log/cvs, not /usr/local/cvsroot.
> >>
> >>Can anyone give me insight into what we're doing wrong here?
> >>

Q1) is $CVSROOT ~=/usr/local/cvsroot/ ?
Q2) did you edit $CVSROOT/CVSROOT/config {to mod the LockDir variable} in
$CVSROOT/CVSROOT/ or did you do a `cvs -d $CVSROOT checkout CVSROOT` and
edit it in the checked out location then do a checkin? Note that except for
the password file, the second method (`cvs checkout CVSROOT`) is the way all
the files in $CVSROOT/CVSROOT should be edited.
Q3) did you do a checkin in $CHECKOUTPATH/CVSROOT?
Q4) was this helpful at all?

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

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