Aside from checking a different script for what you are trying to do here is my USD $.02. the while ( <$socket> ) { function you've defined using <>'s to read the incoming line. AFAIK the brackets are waiting for a \n (carriage return) before executing the loop. I suggest putting some reading into syswrite and sysread to replace your print $socket and while (<$socket>) {. I've used them in a similar situation and they're quite easy to implement. Something like:
syswrite($socket, "$prep rcon $rcon_passwd status\r");
Is the equivalent of the print function and:
while ( (sysread($socket, $incoming, 1024) != 0) { print $incoming; }
Will replace your bracket implementation.

-Adam Stanley
Nethosters, Inc.

In reply to Re: IO::Socket::INET, quake, and me... by astanley
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.