[Top][All Lists]

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

Re: debugging pserver ( protocol )

From: Larry Jones
Subject: Re: debugging pserver ( protocol )
Date: Tue, 3 Jun 2003 11:03:45 -0400 (EDT)

Peschko, Edward writes [in very long lines]:
> what's the protocol for debugging cvs, in particular 'cvs pserver'?
> I'd like to start 'cvs pserver' on the command line,  ping it with
> requests, and break to see where the requests lead..

What I usually do is to run the problematic command in some client/
server mode (usually :fork:) while having $CVS_CLIENT_LOG set to record
the client/server communication into files.  Then I run "cvs server"
under a debugger with it's input redirected from the recorded client
log.  server is identical to pserver except that it doesn't do any
authentication or changing user, so unless you're specifically trying to
debug the authentication code, there's no need to debug pserver instead.
If you are, then you can manually add the authentication information to
the beginning of the client log and then procede as above.

> However, I see from running 'cvs pserver' from the command line, that
> the authentications are taken from stdin. (??) What's going on? Can't
> you say:
> cvs --port=8082 --daemon pserver &
> and have it run in daemon mode?

No.  CVS contains no daemon code since such code is system-specific and
there's no point in duplicating it for every server.  That's what server
managers like inetd are for and CVS, like many other servers, requires

-Larry Jones

Is it too much to ask for an occasional token gesture of appreciation?!
-- Calvin

reply via email to

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