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 out well. On Wed, 2007-08-15 at 13:37 -0400, 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, > > periodically send data to the disconnected client socket <-- NEW > > monitor client socket read status with select() > > > > the select() is not able to see the client socket is dead. > > It might help if you describe exactly what you mean by "periodically send > data to the disconnected client socket". Do you mean periodically queue > more data in the server process? > - > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
