At the last ISP I worked at, the C programmers spent a few days trying to figure out how to kill off open conections, and couldn't find a way. This doesn't mean it ain't there, but it's well hidden.

As for lowering the close timeout, you can recompile your kernel (assuming you have the source :) and change the socket timeout to anything you want. I don't know the effects of changing the timeout, but I feel a great inertiea when it comes to monkeying with TCP.

It is actually fairly easy to fake the responses by monitoring the connections, and then 'injecting' a fake close response at the right time. However this is an unappealing practise.

____________________
Jeremy
I didn't believe in evil until I dated it.

In reply to Re: CLOSE-WAIT sockets by jepri
in thread CLOSE-WAIT sockets by sdyates

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.