Hello,
I hope someone can answer this question:
I have a group called "cvs" of which all users of the cvs repository are
members. If one of those users creates a new directory and adds it to the
repository, cvs identifies the new directory's owner and group name with
that specific user (and as you know, this also happens with files). Now,
when another user tries to checkout or update his local tree, cvs complains
with:
cvs server: Updating top
cvs server: Updating top/mystuff
cvs server: failed to create lock directory in repository
`/vol/cvs/top/mystuff': Permission denied
cvs server: failed to obtain dir lock in repository `/vol/cvs/top/mystuff'
cvs [server aborted]: read lock failed - giving up
...where the new directory created by the first user was called, "mystuff".
The directory, "mystuff" is created in the user's local tree, but none of
the files from that directory (if there are any) are created, and the
checkout (or update) halts. I can change the group ownership of the
directory in the repository to "cvs" and it will work okay, but I don't want
to have to change group ownsership every time a user creates a new directory
in the repository -- that's too much maintenance for the cvs administrator.
Why is this happening, and how do I correct for it?
I am using cvs 1.10.6.
Thanks a lot,
- Dennis Jones
winmail.dat
