info-cvs
[Top][All Lists]
Advanced

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

Re: cvs pserver cmds have become slow on AIX


From: Derek Price
Subject: Re: cvs pserver cmds have become slow on AIX
Date: Tue, 30 Aug 2005 09:34:38 -0400
User-agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)

stephen peterson wrote:

>In my inetd.conf file it envokes the server with the cmdline
>'cvs --allow-root=/<repository-path> pserver'
>per the cederquist guide.  So I figure that pserver protocol is still
>used even though I specify :ext: in place of :pserver: in client cmds.
>  
>

:ext: mode does not go through inetd and does not use :pserver:.  :ext:
mode makes a simple shell connection to your server (via ssh on the
client & sshd on the server) and uses the resulting shell prompt to
launch `cvs server', then begins talking to it.

>Are there any parameters to the cvs cmd when run with the pserver
>argument, that can turn on some sort of logging, to show me more about
>what is going on?
>  
>

Well, running client CVS commands with the global -ttt argument might
help, but I suspect your inetd since, other than performing
authentication, `cvs pserver' operation is almost identical to `cvs
server'.  You could maybe turn on logging via inetd, but I don't really
know.  It is also possible that something in your NIS setup (or, if you
have a CVS server executable compiled with gserver or PAM support,
something in your Kerberos or PAM setup) is causing the delay, for
instance while some authentication daemon tries to connect to a slow or
non-existant network authentication resource.

>Is there a way to envoke cvs with the pserver argument outside of the
>inetd service, so that I don't need to involve the unix administrator
>iin trying cvs in server mode with different arguments?  Has anyone
>written a little program that can be told what port to listen on, and
>pass a connection onto cvs when it comes in, like inetd does?
>  
>

The is the "tcpserver" program, available from this package:
<http://cr.yp.to/ucspi-tcp.html>, is a simple stand-alone listener for a
single port.  You might also try xinetd, but it is probably as lasrge as
inetd and may share some code, FAIK.

Regards,

Derek

-- 
Derek R. Price
CVS Solutions Architect
Ximbiot <http://ximbiot.com>
v: +1 717.579.6168
f: +1 717.234.3125
<mailto:address@hidden>






reply via email to

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