Torben,
If you want to setup multiple pserver processes on a single
host and access each one, then the patch to allow
CVS_CLIENT_PORT will be necessary.
If you only want to change the port used from the default,
then change the port for cvspserver in /etc/services. The
clients, and inetd will resolve the mapping from there.
//Bill
"Derek R. Price" wrote:
Unfortunately, with versions of CVS 1.11 and earlier your
only option is to patch, change the port pserver is
assigned to in your /etc/services file or whatever it is
under AIX that you have to do to get a different result
from getservbyname, or compile a version of CVS after
changing the value of CVS_AUTH_PORT in src/client.c.
Unfortunately, except for the patch, you are still stuck
with the same alternative port every time.
There _is_ an even better fix if you feel like downloading
the dev version of the source from the CVS repository. It
allows you to specify an alternative port as part of
CVSROOT. There's a small issue yet with the treatment of
the password file, but it's no show stopper and I should
have it fixed in another day or two. Of course, you'll
still have to compile that.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
... one of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of their C
programs.
- Robert Firth
Christensen Torben Bach wrote:
Thanks, Derek!
But I still wonder if configuring-by-patching really is
necessary?
I quote from Karl Fogel's CVS-book:
"Before running through the steps needed to set up the
password server,
let's examine how such connections work in the abstract.
When a remote CVS
client uses the :pserver: method to connect to a
repository, the client is
actually contacting a specific port number on the server
machine -
specifically, port number 2401 (which is 49 squared, if
you like that sort
of thing). Port 2401 is the designated default port for
the CVS pserver,
although one could arrange for a different port to be
used as long as both
client and server agree on it. "
Sadly, KF doesn't reveal HOW to arrange it...
/Torben
-Original Message-
From: Derek Scherger [mailto:[EMAIL PROTECTED]]
Sent: 11. januar 2001 02:49
To: Torben B. Christensen
Cc: [EMAIL PROTECTED]
Subject: Re: Connecting to a CVS-server on port *2402*
"Torben B. Christensen" wrote:
Hi there!
All the manuals seems to assume that port 2401 is
always used for a
pserver connection. Well, not on our AIX-box...
So, how do I connect to an alternate port? I know
from our WinCvs
clients that it can be done, but how do I persuade
the
standard UNIX-
client? My best guess would be changing the CVSROOT
- just can't
figure out how...
/Torben B. Christensen
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
There's a patch floating around that allows you to
export
CVS_CLIENT_PORT=2402 before running the client that
I've used
with some
success. I've attached the copy I've used which works
against CVS
1.10.x. If I remember right this is from Derek Price
at Open Ave.
--
Cheers,
Derek
_
Derek Scherger Echologic
Software Corporation
mailto:[EMAIL PROTECTED]
http://www.echologic.com
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
