Jim Wray writes:
>
> In a shared cvs environment over nfs,
Sharing a repository with NFS is a recipe for disaster. We've had
numerous reports of file corruption due to NFS interoperability bugs.
And, unfortunately, repository corruption isn't always obvious and thus
can go undetected for quite a long time, so that when it is detected, it
can be very difficult, if not impossible, to recover. If your NFS
server and clients are all the same kind of systems, you probably won't
have any problems, but if they're not, you're playing Russian Roulette
with your repository. I strongly suggest that you use some form of
client/server CVS instead.
> we cannot share projects without
> allowing users to also modify projects. This is because when checking a
> repository out, cvs needs to write some files in the directory, AND
> setting group write permissions implies group repository write access. We
> need to have the ability for our group to check out the project without
> having write permissions.
http://cvshome.org/docs/manual/cvs_18.html#SEC177
(see LockDir=)
http://cvshome.org/docs/manual/cvs_2.html#SEC36
-Larry Jones
Oh, now don't YOU start on me. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
