I read a thread from last year that mentioned the same type of issue
I am looking to resolve, although I did not find any appropriate
answers. I am looking to set up a cvs pserver, however it will be
located on my hosting provider's machine. I have shell access and
have compiled/installed 1.11
On Thu, Mar 01, 2001 at 04:22:26PM -, Darren Young wrote:
> Now, what I would like to do is something like this:
>
>$HOME/bin/cvs --allow-root=$HOME/cvsroot -T$HOME/tmp -f pserver &
>
> It seems to start fine, although if I touch my keyboard it stops. In
> a second shell session, netsta
ginal Message-
> From: Darren Young [mailto:[EMAIL PROTECTED]]
> Sent: 01 March 2001 16:22
> To: [EMAIL PROTECTED]
> Subject: Standalone CVS pserver
>
>
> I read a thread from last year that mentioned the same type of issue
> I am looking to resolve, although I did not
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:user@host(port):/path_to_cvs_repos
T
run this as a normal user
too. You do not need root privileges to run inetd with a cvs pserver.
I am going to run a cvs pserver with about 40 repositories, which for
some reasons need to be completely distinct, I ran into the problem
that most inetd implementations limit the number of parameters
want to use inetd. You can run this as a normal user
> too. You do not need root privileges to run inetd with a cvs pserver.
>
> I am going to run a cvs pserver with about 40 repositories, which for
> some reasons need to be completely distinct, I ran into the problem
> that most inet
