I don't understand. What would prevent you from using CVS in client/server mode
(unless those that configured it absolutely turned it off) if you're ab;e to use
it in local mode? The only thing I can think of is if the repository is mounted
and you don't have a login to the machine that it's mounted on.
Assuming a default configuration. All one would have to do is set their CVSROOT
properly, possibly set CVS_SERVER, and set CVS_RSH if one isn't using rsh.
Noel
[EMAIL PROTECTED] on 05/14/2000 05:30:21 PM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Noel L Yap)
Subject: Re: CVS problem
> One place I worked for had CVS performance trouble. They were
> using it over NFS, client-server, and a number of other ways.
> After cleaning things up, going completely client-server, and
> using local disk for both the repo, and the client-side, they
> saw at *least* a 10-fold improvement. (Ok, there was a server
> upgrade in there as well...) My "rule" with CVS has always been:
>
> Use client-server, use local disk.
Unfortunately, I have never yet worked in a place where I was allowed
to set up my own CVS server. Or, if I had control over my own machine,
where my CVS server could network across the various intra-company
gateways to all the places where I and others needed to access it.
But, in that same company (which also happens to be the one Michael
is working at) AFS went everywhere.
Going client-server only will make CVS impossible to use for small,
ad-hoc, users who are not officially supported by their companies.
E.g. I use RCS for all of my personal files, .cshrc, etc. I was thinking
of going to CVS, but if CVS is client server only, I will not be able to.
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
