«<Impact>» reads until a newline is received. If the first message is "blank", it's because there was nothing before the first newline.

Update: Well, that's not right. (Tired today.) But then, neither is the question. What is this code you posted, and why isn't it the code that exhibits the problem? You only have one read, yet you talk of the wrong read getting the data you want.

Update: By the way, IO::Socket::INET greatly simplifies the socket creation. 

use IO::Socket::INET qw( );

my $sock = IO::Socket::INET->new(
    Proto    => 'tcp',
    PeerHost => 'axtcnr:6540',
)
    or die("Can't connect to axtcnr:6540: $!\n");

[download]

($sock is already set to autoflush.)

In reply to Re: Socket buffer issue by ikegami
in thread Socket buffer issue by goosesganders

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.