I researched this some more, and now wish to withdraw what I proposed earlier.

The correct way to handle this is to do what golux (++) said.

Here is the sequence of events on failure:

* You attempt to SEND to the client
* Client has closed the socket
* The error is indicated to your program via a $SIG{PIPE}
* You need to trap that signal as golux suggested, and set the value of the global $b_err
* You check the value of $b_err before the next activity on the socket.
* IF triggered, close the client socket, and wait for the client to reconnect (Go back to "accept").

        "Think of how stupid the average person is, and realize half of them are stupider than that." - George Carlin

In reply to Re^5: IO::Socket reconnect by NetWallah
in thread IO::Socket reconnect by nikita.af

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.