TCP keepalive only applies to idle connections. Its purpose primarily
for cases where the local process waits for data from the peer
indefinitely. If the peer disappears or reboots, the connection can tie
up resources forever, so you need a keepalive. However, if the local
TCP sends data, th
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
