Re: Standalone CVS pserver

[Derek R. Price]

John Scott - Outlook wrote:

> I had talked to somebody a while back (can't remember their name now) who
> was looking at makeing a patch to cvs to allow you to specify the port
> number on the command line. Something like setting CVSROOT env var to
> :pserver:address@hidden(port):/path_to_cvs_repos

The current dev version does this.  The syntax is 
:pserver:address@hidden:port]/path_to_cvs_repos


> Also I didn't think that pserver listened on a port for you. It was designed
> so that inetd would listen on the port and spawn the cvs pserver command
> when a connection was made, after tying the socket connection to the stdin
> stream of the spawned process. - This is only what I have observed and I may
> well be way off the mark...
>
> This is acomplished by putting the following in the inetd.conf file (all on
> one line):
>
> cvspserver      stream tcp nowait root /path_to_cvs/cvs cvs
> --allow-root=/mware/cvsroot -f pserver

Yeah.  inetd is the way it is supposed to be set up.  pserver expects its input 
on stdin, so when you background it, the shell closes stdin and cvs reads EOF 
and quits.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden     OpenAvenue ( http://OpenAvenue.com )
--
I will not show off.
I will not show off.
I will not show off...

          - Bart Simpson on chalkboard, _The Simpsons_