An easier way to look at the pserver client/server dialog is to define the
CVS_CLIENT_LOG environment variable with the base file name for the log on
the client. The client will create two files. Everything that the client
sends to the server is logged in filename.in and everything from the server
is in filename.out.
This is documented in Cederqvist
(http://www.cvshome.org/docs/manual/index.html), specifically in
http://www.cvshome.org/docs/manual/cvs_19.html#SEC178
- Tim
> -----Original Message-----
> From: Laird Nelson [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 14, 2000 10:51 AM
> To: [EMAIL PROTECTED]
> Subject: inetd question related to cvs (not usual pserver doesn't work
> FAQ)
>
>
> inetd programs are supposed to be able to simply read from STDIN,
> right? I'm trying to write a wrapper program around cvs pserver that
> gets invoked, obviously, from STDIN. I'd like to peek at the
> conversation between client and server, and I thought I could get at
> this conversation by simply reading from STDIN. But my program blocks
> infinitely. Is the cvs client/server protocol such that it is started
> by the server (the Cederqvist says no)?
>
> In case it matters, my program is a perl program.
>
> Cheers,
> Laird
>
