If you're using 'telnet' to connect to port 9000, be aware that telnet will interpret your newlines as "\x0d\x0a", not a straight Perl \n. Thus, chomp will only rid you of the "\x0a" (what \n evaluates to under Unix, as in $/). Try either setting $/ to "\x0d\x0a" while processing data from the socket like that, use chop twice, or just use this regexp: s/\x0d\x0a$//;

When in doubt, I've been known to simply do this when I don't know how the lines end: s/[\r\n]+$//;

In addition, your print statement to OUT doesn't have a trailing newline, so your log file doesn't have an end-of-line to act on (stdio buffering does this, I believe). That's probably why you aren't seeing any of this ending up in the log file.

In reply to Re: File I/O while using Sockets? by Fastolfe
in thread File I/O while using Sockets? by jgallagher

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.