[Top][All Lists]

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

Re: Hung CVS server processes

From: Dan Peterson
Subject: Re: Hung CVS server processes
Date: Mon, 30 Sep 2002 21:11:48 -0700 (Pacific Daylight Time)

On Fri, 27 Sep 2002 address@hidden wrote:

> Dan Peterson writes:
> >
> > Under what circumstances will a CVS client stay connected to the
> > server without doing ANYTHING?  Does this depend on the type of
> > client?  Or are there some commands that will stay connected?
> The only time I can think of that the standard client intentionally
> stays connected without doing anything is during a commit when it's
> waiting for the user to finish editing the log message.  There's also an
> interoperability bug between the 1.11.2 server and pre-1.11.2 clients
> when using compression (the global -z option) where both the client and
> the server wait (forever) for the other side to close the connection
> first.

Well, I may have spoke a little too soon.  I was correct in saying the
connection is still active... and I THINK I was correct in saying there
was no activity (other than keepalive packets) for at least 22 hours.
But right after I killed the "snoop" process 24 more packets were suddenly
captured.  At least some of these packets contain CVS protocol commands.

It seems a little strange to me that these additional packets appeared
just as I killed the "snoop" process... almost like they were buffered,
but never sent to the capture file.  The funny thing is, if they were
buffered, then I'd expect the time stamps to be spread out over a long
period of time, but they aren't, the timestamps are all within a few

When I asked the Sun SE about this he said he could think of no reason the
keepalive packets would have been captured real-time and the other packets
buffered.  So, he suspected it was just a coincidence the new packets came
right when I killed the process.

At any rate... it still raises the question of why the connection stays
open and apparently connected to a CVS client.  So let me rephrase my
previous question a little...

Does the CVS pserver protocol allow a client to stay connected after
completing a particular command?  And subsequently be able to execute
multiple commands on the same connection?

If so, are there any CVS clients that will stay connected all the time?

reply via email to

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