I thought that "broken pipe" only happened when writing to a pipe (and my quick review of some documentation supports that)...

But it would make sense that a socket could give you "broken pipe" on read if the connection was broken badly (as opposed to the connection being shut down normally which should just generate "end of file" which sysread will return as 0 and not undef).

So, for example, the connection timing out or the route to the client being lost (to the point of generating "host unreachable" via ICMP), etc. could probably generate this.

        - tye (but my friends call me "Tye")

In reply to (tye)Re: Unexplainable Client/Server trouble by tye
in thread Unexplainable Client/Server trouble by astanley

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.