On Tuesday 17 September 2002 12:40 pm, [EMAIL PROTECTED] wrote: > > We've been using CVS with the repository exported via NFS to our UNIX > > boxen. > > This seems to cause an undue amount of repository file corruption, and > should be avoided.
Yah, I know. I've been trying to change it to using ssh, but keep getting "but... it works now" from TPTB. > > > now we need to connect to another cvs repo at a remote site and the only > > access the want to give us is via wincvs with the repository on a mapped > > drive. > > What do you mean with the repository on a mapped drive? If it's at a > remote site, use some sort of client-server system, either ssh or > pserver depending on your needs. This should be much less intrusive > than somehow NFS-mounting the drive from afar. > That's why I'm basically collecting ammo. They want us to use wincvs with a SMB mounted repo. Since I use FreeBSD this presents something of a problem. > > Could someone explain to me the issues with mounting the repo via a > > network filesystem? > > In the first place, it exposes the repository to anything anybody might > do to it, whereas client-server restricts what somebody can do to the > repository while making a mistake. > > In the second place, it seems to cause data corruption. This is probably > a case of locking problems, so that more than one server process will > be working on the same directory without realizing it. Thanks. That's what I need to try to convince them to DTRT. Thanks also to everyone else who replied. More ammo's always good :) -- [EMAIL PROTECTED] Matthew Navarre It was a hard sell, since he's a database person, and as far as I've seen, once those database worms eat into your brain, it's hard to ever get anything practical done again. To a database person, every nail looks like a thumb. Or something like that. - jwz _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs