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
PROTECTED]
|
| cc:
|
| Subject: checkout/commit onto
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 17 June 2003 13:10
To: David Bowring
Cc: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: checkout/commit onto/from shared disks.
what is your concern?
The only one that I can see would be large files with frequent changes
over
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.
Max Bowsher wrote:
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
David Bowring writes:
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
Riechers, Matthew W writes:
As anecdotal evidence, I'd submit that I have been hosting several sandboxes
on NFS shares for years without incident. As long as the path between the
client and server is not over a network sharing system, you shouldn't have a
problem.
NFS mounted working
[ On Tuesday, June 17, 2003 at 10:27:21 (-0400), Larry Jones wrote: ]
Subject: Re: checkout/commit onto/from shared disks.
All of the known NFS problems are interoperability problems between
different NFS implementations.
Well there can also be generic NFS problems between server and client
[ On Tuesday, June 17, 2003 at 13:03:52 (+0100), David Bowring wrote: ]
Subject: checkout/commit onto/from shared disks.
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
Greg A. Woods writes [quoting me]:
All of the known NFS problems are interoperability problems between
different NFS implementations.
Well there can also be generic NFS problems between server and client of
the same implementation. For example NetBSD has full support for file
locking
Hollingsworth
--- Greg A. Woods [EMAIL PROTECTED] wrote:
[ On Tuesday, June 17, 2003 at 13:03:52 (+0100), David Bowring wrote: ]
Subject: checkout/commit onto/from shared disks.
This would comprise of one central server upon which all the developers
home directories and cvs server would reside
[ On Tuesday, June 17, 2003 at 11:38:41 (-0700), Kristopher Hollingsworth wrote: ]
Subject: Re: checkout/commit onto/from shared disks.
This is more or less what I'm trying to set up, Checkout/commit over
a small LAN here. Everything would be over shared drives, but I
don't know how
Yeh... That'd be nice, I'll see what I can't talk them in to doing... Oh well,
Thanks for the help, it's appreciated.
-Kristopher G. Hollingsworth
--- Greg A. Woods [EMAIL PROTECTED] wrote:
I think you're in the wrong newsgroup/mailing-list. As far as I know
this CVS doesn't run
A. Woods [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 4:11 PM
To: [EMAIL PROTECTED]
Cc: CVS-II Discussion Mailing List
Subject: Re: checkout/commit onto/from shared disks.
[ On Tuesday, June 17, 2003 at 11:38:41 (-0700), Kristopher Hollingsworth
wrote: ]
Subject: Re: checkout/commit
14 matches
Mail list logo
