info-cvs
[Top][All Lists]
Advanced

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

Re: cvs join update


From: Larry Jones
Subject: Re: cvs join update
Date: Tue, 28 Dec 2004 00:07:35 -0500 (EST)

Murugaiyan, Natarajan [IT] writes:
> 
> Why does cvs join update command
>       cvs -d /opt/fdtssrc/gfdtssrc1 update -j HEAD
> try to acquire a lock in the repository?

To prevent someone else from updating the repository file while the
update is in the process of reading it.

> I am using CVS 1.11.6 in Solaris 8 and above command fails with this error 
> message:
>         cvs update: failed to create lock directory for 
> `/opt/fdtssrc/gfdtssrc1/tkbatch' (/opt/fdtssrc/gfdtssrc1/tkbatch/#cvs.lock):  
> Permission denied
>         cvs update: failed to obtain dir lock in repository 
> `/opt/fdtssrc/gfdtssrc1/tkbatch'
>         cvs [update aborted]: read lock failed - giving up

That indicates that you do not have write permission in the repository
directory, which means that you won't be able to commit changes.  If
that's what you want (read-only access), then you just need to set
LockDir= in your $CVSROOT/CVSROOT/config file to have CVS put the lock
files somewhere other than in the repository where you do have write
access.  If you don't want read-only access, you need to set the
ownership and permissions on the repository directories correctly.  See
the manual for details:

        <https://www.cvshome.org/docs/manual/cvs-1.11.18/cvs_2.html#SEC13>

-Larry Jones

Good gravy, whose side are you on?! -- Calvin




reply via email to

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