I asked:
>What are the pros and cons of using NFS to access the CVS repository
>between systems that are similar? What if the OS version isn't
>exactly the same?
>
>We have been using CVS like this for a while. I would like to
>know if it is worth setting up a cvs server on our file server. The
>sysadmin has to do this and be comfortable with it because he is the
>only one who can login to the file servers.
Todd Denniston answered:
>An easier method, to implement and thus more worth setting up, might be rsh to
>one central box that has access to the repo dir. If you already use rsh/ssh
>between machines in the office it is fairly easy to just change everybody's
>$CVSROOT to point to ":ext:open_machine_name:/path_to/repo" also you may need
>to set $CVS_SERVER if for some reason the server's cvs binary is not found on
>the path provided to the shell.
Thank you all for your suggestions. Todd's suggestion seems like the
best fit for our environment. It's also easy to set up. We have a
workstation picked to use as the primary CVS server for our
repository. I will put a commitinfo script to check the hostname and
warn people to change their CVSROOT if they are checking in from
another machine. At some time in the future (after we have fixed up
everyone's CVS/Repository and .cshrc or whatever), that warning will
turn into an error.
Fred
--
==
Fred Brehm, Sarnoff Corporation, [EMAIL PROTECTED]
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
