There is indeed no need of an eval, Unfortunately selecting for writability (or readability for EOF) doesn't solve the real problem, which is SIGPIPE as result of writing to a closed socket. And that close can happen after the select told the socket was writable but before you got to doing the write. The conventional solution in socket programming is to simply ignore SIGPIPE (usually even globally) and use the returncodes of the I/O operations instead.

$SIG{PIPE} = "IGNORE";
....
print($socket $string) || die "Error writing to socket: $!"

[download]
(or do something else than die of course, or catch the die in some enclosing eval)

In reply to Re^2: Trapping socket error in client when server goes away by thospel
in thread Trapping socket error in client when server goes away by Anonymous Monk

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.