Alan Cox wrote:
> > > First obvious comment. It doesn't enforce the 2hr timeout minimum. The
> > > minimum of 1 is wrong for some of those values.
> >
> > Yes, the minimum values can be the values you decide they should be.
>
> Then people will abuse it.
>
> > Even though from my experience with Tru64 and pSOS they can be as low as 1
> > (but of course I do not argue that these TCP stacks are the best).
>
> Those stacks are broken if they allow you to set it below 2 hours.
I do not understand why it is broken to lower the value below 2 hours when it
can be lowered
even now in linux system wide. Try echo
2>/proc/sys/net/ipv4/tcp_keepalive_time. Then all keepalive
will take place even at linux after 2s (actually within 4*75s due to current
logic in handling keepalive).
Why not to allow the system default time to be default 2hours
and only applications which decides to do so to lower this per socket.
The RFC 1122 says that it MUST be configurable and MUST default to no less than
2 hours.
The "default" is satisfied and there is no restriction in lowering it. So by my
opinion the linux
will be broken when it will enforce 2hours timeout and the Tru64 is right.
Lowering it is in general allowed.
Pavel
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
