Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I am embarking on a great undertaking. I'll refrain from talking about it here because it's not really important to the question. I ask this question because I'm being befuddled on the first step.

My program telnets into a MUSH, using open MUX_OUTPUT, "|telnet host.server.net 8080 > logfile" It telnets in correctly, the logfile gets the expected output that the MUSH sends back, however, I cannot print commands to the MUSH. I have unbuffered my output with $|=1. I have tried sending commands ending in \n \r \f and many combinations thereof. I got it to work in C using popen(), \n, and manually flushing the buffer after each write, but this doesn't seem to work at all in the holy language of PERL. Any ideas what I'm doing wrong?

~W

In reply to Sending commands to a Telnet Server by wombat

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.