By default, , on a UNIX box, when forking, the open handles are inherited from the father
so this is not surprising that STDIN and STDERR are sockets if the father has opened sockets.
IIRC a process can "restore" STDIN, STDOUT and STDERR if not detached of the current tty.
For a start, try to adpat the following code that reopens the STD* handle:
close STDIN; close STDOUT; close STDERR; # not really necessary
open STDIN, "</dev/tty";
open STDOUT, ">/dev/tty";
open STDERR, ">/dev/tty";
# testing
print "STDOUT\n";
print "STDERR\n";
$_ = <STDIN>;
print $_;
Really, these are not Perl issues. They are thouroughly
covered in
Advanced Programming in the UNIX Environment by Richard Stevens. I really need to reread it from cover to cover.
I would be happy to learn that there is a more portable way to reopen this file handlles.
-- stefp
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.