[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: shifting from pserver method to ext method

From: Eric Siegerman
Subject: Re: shifting from pserver method to ext method
Date: Fri, 2 May 2003 13:08:24 -0400
User-agent: Mutt/1.2.5i

On Fri, May 02, 2003 at 06:25:35AM -0000, mehul  choube wrote:
> i am thinking of shifting [from pserver] to ext method connection. what 
> changes i will
> have to undertake?

Off the top of my head:
 1. Get SSH working between the various machines concerned.
      - "Working" means that you can "ssh cvs-server date" (or
        some other command that the server supports) from all the
        client machines to the CVS-server machine.  (In theory
        you could use rsh instead of ssh, but it's so insecure
        that you might as well stick with pserver :-)

      - It's probably worth spending the extra time to figure out
        the ssh-agent stuff; otherwise, people will be doing a
        *lot* of password-typing.  That gets annoying pretty
        quickly, and your users will hate you if you impose it on

 2. On the client machines, set the CVS_RSH and CVS_SERVER
    environment variables appropriately (see the docs).
      - Note that CVS_SERVER should contain the *local* pathname,
        on the server machine, of the CVS binary.  It does *not*
        contain a host name.  I found this a bit confusing at
        first, since you set the variable on the clients.

 3. Check out a new sandbox (for testing, you can check out a
    small subset of your project), using an ext-style repository
    specifier instead of a pserver-style one

When you're ready to go live with the new setup:
 4. Get your users to check out new sandboxes as in (3), or else
    to rewrite all their CVS/Root files

 5. Disable pserver (the most thorough, and therefore safest, way
    is probably to comment out that line in inetd.conf; don't forget
    to goose inetd).

I've separated steps (1) and (2) for a reason.  You'll save
yourself a *lot* of grief if you get SSH working on its own
before you bring CVS into the picture.  If you try to debug the
SSH link in the context of CVS, there'll be too many variables;
if there's a problem, it'll be *much* harder to figure out
whether it's on the SSH or CVS side of things.


|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
My Wine works.  However it crashes about half the time on startup.
Apparently their simulation of windoze API is getting too accurate.  :)
        - Kyle Sallee

reply via email to

[Prev in Thread] Current Thread [Next in Thread]