Excellent... that seems to fix the STDOUT problem... but when I do that for STDIN it does not seem to work. 
  open(STDIN,"<&".fileno($c)) or die;
  print STDERR "STDIN: ",<STDIN>;
  print STDERR "\$c: ",<$c>;

[download]
gives me: 
20040902 14:15:45 STDIN: 
20040902 14:15:45 $c:  fcl_userid=d4ants&fcl_password=hidden&referer=&
+fcl_login_submit=Login

[download]
very strange. This I can deal with.. the STDOUT was the more important thing, STDIN would just be a nice thing to get working.

I had manged to get it working using POSIX::dup2 and POSIX::close... but this seems much nicer :)

Thanks!

                - Ant
                - Some of my best work - (1 2 3)

In reply to Re^2: STDOUT changing descritpors (open, no =) by suaveant
in thread STDOUT changing descritpors by suaveant

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.