[Top][All Lists]

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

Re: CVS and RSH--please clarify

From: Mike Castle
Subject: Re: CVS and RSH--please clarify
Date: Wed, 12 Sep 2001 20:58:42 -0700
User-agent: Mutt/1.3.18i

On Wed, Sep 12, 2001 at 04:25:28PM -0700, Paddy T wrote:
> In most machines here,CVS works fine even though rsh
> is not installed at all in that machine.
> We have our CVSROOT set as :server: for all

Apparently :server: users an internal rsh implementation.

> developers(except those working on linux who have
> :ext:) which according to the manual uses rsh to

Which appears to not be available on the unix version (more likely, not
available by default).

> perform cvs operations.So how is cvs working from
> these machines?

one on of the linux boxes, do something like "cvs -t up".  The -t turns on
some tracing, and you can watch it execute the rsh command.

Most likely cvs uses standard pipe() followed by a fork()/exec() to spawn
rsh in such a way that stdin/stdout of the rsh command is tied to the pipe.
The rsh command executes the cvs command with the option server on the
remote machine.  That remote cvs process then uses the cvs protocol across
it's stdin/stdout (which is tied to the local machine's pipe) and does all
of it's network stuff.  For the nt part, the stuff that rsh does is built
into the binary, and so it's your usual open a socket and connect to a port
type of stuff.  Only in this case, the port is the rcmd(?) port, which
fires up the rshd, and cvs then tells the shell rshd gives it to start "cvs


> Also is it mandatory that we should we use :ext for
> linux clients?

Probably.  It might be possible to build the linux version with :server:
support, but why bother :ext: works?

     Mike Castle      address@hidden
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

reply via email to

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