[Top][All Lists]

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

Re: pserver processes

From: Larry Jones
Subject: Re: pserver processes
Date: Thu, 25 Oct 2001 11:22:56 -0400 (EDT)

Mark writes:
> there seems to be cvs pserver processes hanging around after the respective
> client has gone on to bigger and better things.

What release of CVS and what platform?

That indicates that clients are going away without properly closing
their connections to the server.  That shouldn't happen unless the
client machine crashes or there's some kind of network failure.  Because
of the way TCP/IP works, the server doesn't have any way to know that
that has happened until it tries to send data to the client.  If the
server is reading data from the client rather than writing, it will
never receive any notification.  Whenever possible, pserver uses the
KEEPALIVE option on its sockets which is supposed to cause the OS to
periodically send "Are you still there?" packets across idle connections
to detect this condition -- it's possible that KEEPALIVE either isn't
available on your platform (or the configure script thinks it isn't for
some reason) or doesn't work correctly.  It's also possible that you
just haven't waited long enough: most systems have fairly long timeouts
to avoid dropping connections due to temporary network problems (RFC1122
prohibits sending KEEPALIVE packets until a connection has been idle for
at least two hours).

-Larry Jones

Oh yeah?  You just wait! -- Calvin

reply via email to

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