TIME_WAIT

[rick jones]

if there are large numbers of TCP endpoints in CLOSE_WAIT it implies that the local app has ignored the notification that the remote has closed its end of the connection. or...

If the local side is in CLOSE_WAIT, the other side is likely in FIN_WAIT_2. Given that FIN_WAIT_2 can be a perfectly valid recv-only state, CLOSE_WAIT can be a perfectly valid send-only state.

so, i would really strongly caution anyone against using that ndd kludge to sumarily nuke a TCP connection.

if the connection is in CLOSE_WAIT and the app has no concept of a send-only connection, the app is buggy and is ignoring the remote close indication. such an app REALLY needs to be fixed. the ndd junk is merely a bandaid and it will not cure the disease.

[rick jones]

there is a small, but vitally important typo in rajman's discussion of setting tcp_time_wait_interval for HP-UX 11.

the units are _milliseconds_ not seconds.

another reason the default TCP timers should be left along I supose :)

[Dave van Nierop]

Kudos Rick! Great advice ...