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 a slow network. But even that wouldnt seem like much of an issue. Tom |-+- | | David Bowring | | | [EMAIL PROTECTED] | | | Sent by: | | | info-cvs-bounces+thomas.maciejewski=us.socgen.| | | [EMAIL PROTECTED] | | | | | | | | | 06/17/2003 08:03 AM | | | | |-+- --| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: checkout/commit onto/from shared disks. | --| 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. Thanks Dave B. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ** The information contained herein is confidential and is intended solely for the addresse(s). It shall not be construed as a recommendation to buy or sell any security. Any unauthorized access, use, reproduction, disclosure or dissemination is prohibited. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall assume any legal liability or responsibility for any incorrect, misleading or altered information contained herein. ** ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: checkout/commit onto/from shared disks.
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. Cheers -Original 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 a slow network. But even that wouldnt seem like much of an issue. Tom |-+- | | David Bowring | | | [EMAIL PROTECTED] | | | Sent by: | | | info-cvs-bounces+thomas.maciejewski=us.socgen.| | | [EMAIL PROTECTED] | | | | | | | | | 06/17/2003 08:03 AM | | | | |-+- --- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: checkout/commit onto/from shared disks. | --- ---| 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. Thanks Dave B. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ** The information contained herein is confidential and is intended solely for the addresse(s). It shall not be construed as a recommendation to buy or sell any security. Any unauthorized access, use, reproduction, disclosure or dissemination is prohibited. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall assume any legal liability or responsibility for any incorrect, misleading or altered information contained herein. ** ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: checkout/commit onto/from shared disks.
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
Re: checkout/commit onto/from shared disks.
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 network throughput issue. AFAIK, the corruption issues relate to storing the repository itself on a network share. 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. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: checkout/commit onto/from shared disks.
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 or foresight of any pit falls with such a mechanism, it would be gratefully appreciated. All of the known NFS problems are interoperability problems between different NFS implementations. Your proposed setup uses the same NFS implementation on all the machines, so it should work just fine. -Larry Jones I always have to help Dad establish the proper context. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: checkout/commit onto/from shared disks.
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 directories are just as problematic as NFS mounted repositories, it's just that the chances of having a problem are usually smaller (since the repository is more heavily used than a working directory) and the consequences of having a problem are less severe. If it works for you, then more power to you; I've been running an NFS mounted repository for years without incident, but I don't recommend it to others. -Larry Jones Apparently I was misinformed. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: checkout/commit onto/from shared disks.
[ 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 of the same implementation. For example NetBSD has full support for file locking in the server, but none in the client. However for working directories there can be no more problems with NFS than there would be with any other ordinary file using application on NFS since there should never be more than one CVS process active in any given working directory at any time. -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: checkout/commit onto/from shared disks.
[ 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 (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. There is no problem with CVS sandboxes on NFS. However in such a scenario it would be not just unwise to use cvspserver, but unnecessary as well. Just use rsh! Rsh is FAR more secure than NFS. -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: checkout/commit onto/from shared disks.
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 in the server, but none in the client. Perhaps I should have said, ... problems with CVS ... -- CVS doesn't use file locking. -Larry Jones I obey the letter of the law, if not the spirit. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
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 to setup the CVSServer, so if someone could point me to some documentation on this or any other help towards that end... The Repository would be on this machine which is Windows 98 (I should be able to come up with a more elegant setup in the future, but for now, I really just need this to work as it is.) With two other Windows machines accessing the repository. Anyway... Thanks in advance for any help... -Kristopher 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. 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. There is no problem with CVS sandboxes on NFS. However in such a scenario it would be not just unwise to use cvspserver, but unnecessary as well. Just use rsh! Rsh is FAR more secure than NFS. -- Greg A. Woods _ Free email at www.Z6.com ( and home of worldmap.com) _ Select your own custom email address for FREE! Get [EMAIL PROTECTED], No Ads, 6MB, IMAP, POP, SMTP more! http://www.everyone.net/selectmail?campaign=tag ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: checkout/commit onto/from shared disks.
[ 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 to setup the CVSServer, so if someone could point me to some documentation on this or any other help towards that end... The Repository would be on this machine which is Windows 98 (I should be able to come up with a more elegant setup in the future, but for now, I really just need this to work as it is.) With two other Windows machines accessing the repository. Anyway... Thanks in advance for any help... I think you're in the wrong newsgroup/mailing-list. As far as I know this CVS doesn't run as a server on M$-Windows-98. There is supposedly a version of CVS available for M$-NT, but it has its own user-support mailing list. In any case *I* would strongly recommend burning your Windoze install and putting something like FreeBSD, NetBSD, or Linux on your server, or even some commercial UNIX System(TM). :-) -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: checkout/commit onto/from shared disks.
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 as a server on M$-Windows-98. There is supposedly a version of CVS available for M$-NT, but it has its own user-support mailing list. In any case *I* would strongly recommend burning your Windoze install and putting something like FreeBSD, NetBSD, or Linux on your server, or even some commercial UNIX System(TM). :-) -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] _ Free email at www.Z6.com ( and home of worldmap.com) _ Select your own custom email address for FREE! Get [EMAIL PROTECTED], No Ads, 6MB, IMAP, POP, SMTP more! http://www.everyone.net/selectmail?campaign=tag ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: checkout/commit onto/from shared disks.
Greg, I have recently rejoined the CVS community and have come to the conclusion that you are one of the most unhelpful people on the list. You sound like a throw back to 10 or more years ago when the net was free and attitudes like yours flourished. Bert -Original Message- From: Greg 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 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 to setup the CVSServer, so if someone could point me to some documentation on this or any other help towards that end... The Repository would be on this machine which is Windows 98 (I should be able to come up with a more elegant setup in the future, but for now, I really just need this to work as it is.) With two other Windows machines accessing the repository. Anyway... Thanks in advance for any help... I think you're in the wrong newsgroup/mailing-list. As far as I know this CVS doesn't run as a server on M$-Windows-98. There is supposedly a version of CVS available for M$-NT, but it has its own user-support mailing list. In any case *I* would strongly recommend burning your Windoze install and putting something like FreeBSD, NetBSD, or Linux on your server, or even some commercial UNIX System(TM). :-) -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
