[Top][All Lists]

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

RE: write lock error?

From: Teala Spitzbarth
Subject: RE: write lock error?
Date: Thu, 16 Aug 2001 11:38:35 -0700

What about the directory perms of the actual takeme directory?
Is that more restricted?

If you are running on Linux you will probably want to 
use the setgid bit on  /repository so that all subdirectories
that get created in the repository get the cvs group ownership.
If takeme is already created with more restictive perms you 
will have to set the setgid bit on that as well.

See RH documentation for more info:

Your reboot should be completely orthogonal to the perms issue....
don't thrash.


-----Original Message-----
From: Ronald Edward Petty [mailto:address@hidden
Sent: Thursday, August 16, 2001 11:08 AM
To: address@hidden
Subject: write lock error?

My message is attached.  Sorry I mistyped the address, and dont know how
to cut and paste through a term.


I have reread info cvs and the docs.  I still cannot see how
am getting this

cvs checkout takeme
cd takeme
touch a
cvs add a
cvs commit a
cvs commit: failed to create lock directory for
`/repository/takeme/#cvs.lock): Permission denied
cvs commit: lock failed - giving up

I am the user cvs, who is in the group cvs, who owns the CVSROOT which
/repository.  The permissions of the CVSROOT is

drwxrwxr-x      4 cvs   cvs             4096 Aug 15 13:51 repository

I have also tried using other members of the cvs group and get the same
errors.  If the group permission is rwx, how come they cannot write to
I did cvs init after I rebooted the machine using the user cvs.  Does
have to do this or something?  I am confused, the documentation on info
cvs seems to say you have to create the locks yourself.... am I wrong?
Looks to me like its trying but can't, Im no sys adm so I am not sure
is going on.

Thanks for the help

reply via email to

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