David Bowring wrote: > My concerns were merely that I had heard noises about using CVS on disk > shares and was worried (in some part) about corruption, though I could > not foresee it. All the clustered machines will be on a Gigabit > backbone, so this should negate the network throughput issue.
AFAIK, the corruption issues relate to storing the repository itself on a network share. Max. > -----Original Message----- > From: [EMAIL PROTECTED] > > what is your concern? > The only one that I can see would be large files with frequent changes > over > a slow network. But even that wouldnt seem like much of an issue. > Tom > >> ---------+---------------------------------------------------------> >> | "David Bowring" | >> | <[EMAIL PROTECTED]> | >> ---------+---------------------------------------------------------> > > Hi, > > I'd like to start by thanking everyone for the advice I've received from > previous posts...so thank you all. > Alas, I once more seek your advice though. I intend to build a > clustered linux solution for our developers to use. > This would comprise of one central server upon which all the developers > home directories and cvs server would reside. They will be logged into > any one of many machines (nodes). My concern is being that each of our > developers home directories will be a disk share from the central > machine, and all the checkout/commit will be done via pserver onto these > shares (I am considering using NFS to create the shares). If anyone can > give me any guidance or foresight of any pit falls with such a > mechanism, it would be gratefully appreciated. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
