:>
:> If they are spaced too far apart, it is possible for perfectly
:> legitimate connections to get shot down as a result of external
:> periodicities. (Does somebody's router reset every day at 2:45? If
:> so, better hope no keepalives are scheduled for then!)
:
:But remember that the idea is the keepalive would keep trying for a certain
:amount of time, and this would be finely configureable.
: Brian Feldman _ __ ___ ____ ___ ___ ___
Adjusting the keepalive's retry period after activation is also
irrelevant. As they currently stand, keepalives operate in virtually
the same fashion as sending a byte of data. Extending the retry
period for a keepalive is no more a reliable solution then extending
( or shortening ) the initial timeout because you are only effecting one
small aspect of the TCP protocol. You are not effecting timeouts
associated with normal data transmitted ( from either side ) over TCP.
Unless the entire purpose of the connection is to simply be connected,
with no data flow ever, being able to finely tune keepalive values does
not really help. The existing rough tuning is as much as anyone will
ever need to mess with.
-Matt
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
