Your problem could probably be fixed by placing the socket in non-blocking mode. When in non-blocking mode it is gaurenteed that your process will not block from operations on the socket. However, this means that you should check the return values of all your reads (and writes, maybe) in case they return an error ( for when blocking would have occured, EAGAIN ("Resource temporarily unavailable" (but locale can change that message)); the Errno module will be helpful.) You can turn blocking off with: 

$sock->blocking(0);

[download]

Note that IO::Select provides an alternate select interface that you aren't using. You do not need to use a module to use the built-in select interface.

Note that when sysread returns 0 that means EOF.

In reply to Re: socket reading... by wog
in thread socket reading... by jdv79

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.