mer associated with the socket keepalive algorithm is reset upon
actually receiving traffic from the remote socket.
Is this the intended behavior of the TCP keepalive algorithm, or a bug?
[kernel = 2.4.27 on i686]
TIA,
Jeff
-
To unsubscribe from this list: send the line "unsubscri
On one of my servers I've tuned keep alive down to 300 seconds. We have
a program that reads only from a remote device. If that remote device
dies I need to know as fast as possible. 7200s is just too long of a
wait. I'm not suer how much overhead this places on the network but it
seems to work
On Wednesday 15 August 2007 12:37, Charlie Brady wrote:
> On Wed, 15 Aug 2007, Jeff Weber wrote:
> > However, if I:
> >
> > b)
> > enable TCP keepalive on a server,
> > lower the default keepalive parameters,
> > establish a connection from a client,
> > physically disconnect the server network,
>
On Wed, 15 Aug 2007, Jeff Weber wrote:
However, if I:
b)
enable TCP keepalive on a server,
lower the default keepalive parameters,
establish a connection from a client,
physically disconnect the server network,
periodically send data to the disconnected client socket <-- NEW
monitor client s
ive algorithm is reset upon
actually receiving traffic from the remote socket.
Is this the intended behavior of the TCP keepalive algorithm, or a bug?
[kernel = 2.4.27 on i686]
TIA,
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of
