No, that has nothing to do with IO::Socket::INET. It has to do with <$sock> also known as $sock->readline(); which won't return until either $/ is read or end-of-file. Killing the client closes the socket which sends end-of-file (as would using shutdown).

This is part of the reason one should normally not use <$sock> but instead should use sysread (or similar). Even if your protocol adds newlines on the end of each "packet", using <$sock> makes it hard to debug what broke when things go wrong.

- tye        

In reply to Re^2: IO::Socket::INET, quake, and me... ($/) by tye
in thread IO::Socket::INET, quake, and me... by snafu

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.