Yes, by default writing to a closed socket will cause your program to receive a SIGPIPE, which by default will kill it. (See 'man 2 write', search for EPIPE).

You can ignore or handle the signal (see %SIG in perldoc perlvar), in which case you'll get an error returned from the write and $! will be set to EPIPE (in a numeric context, or the error string in a string context).

Linux is giving you some default error handling (killing your process via SIGPIPE), if you want something more complex you'll need to check for and handle errors as above. Good luck.

In reply to Re: program dies when printing to closed socket, I think by jbert
in thread program dies when printing to closed socket, I think by HansB

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.