New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perl's fork resets open filehandles in parent process #5970
Comments
From SCUSACK@bloomberg.netCreated by scusack@bloomberg.neterr.in: 1234567890 err.pl: #!/usr/local/bin/perl print "without fork, this works:\n"; print "with fork, even though the child does nothing, this loops forever, ". Perl Info
|
From @eserte"SEAN CUSACK, BLOOMBERG/ 499 PARK" (via RT) <perlbug@perl.org> writes:
Maybe this is Solaris specific. I can't reproduce the problem on Regards,
-- tktimex - project time manager |
From SCUSACK@bloomberg.netSlaven, Yes, it is solaris-specific. But is there anything perl itself can do to have --Sean |
From @HugmeirOn Tue Oct 01 15:01:12 2002, scusack wrote:
I could reproduce this on Solaris 10 with the system-provided 5.8.4, but |
@cpansprout - Status changed from 'open' to 'resolved' |
From @nwc10On Sat, Apr 28, 2012 at 02:22:39AM -0700, Brian Fraser via RT wrote:
I ran this with the test script tweaked with C<alarm 10;>: ../perl/Porting/bisect.pl --expect-fail --target miniperl --start perl-5.8.0 ../17711.pl It says: commit 15b61c9 Introduce two new Configure symbols: p4raw-id: //depot/perl@19286 :100755 100755 f7a40505e0d66103dd6a89983c12ea1a3309ed36 b8116b9c362c6e572854470492ac89086913e400 M Configure So, if I try the script with system perl like this: $ PERLIO=perlio perl ../17711.pl it now exits cleanly rather than looping. and if I run blead (ish - what I had handy) like this: $ PERLIO=stdio ~/Sandpit/R/bin/perl5.15.2 ../17711.pl it loops, as before. So, at this point, it looks like this bug isn't totally resolved. *Except*, this is the man page for fork(2) on Solaris: NOTES SunOS 5.11 Last change: 28 Oct 2008 6 System Calls fork(2) buffered data twice. See exit(2). [I'd already tested that replacing exit() with POSIX::_exit() made it So, the program using exit() is hitting a documented caveat of Solaris Nicholas Clark |
From @cpansproutOn Tue May 01 03:27:12 2012, nicholas wrote:
Do you suggest we re-open it, then? -- Father Chrysostomos |
From @nwc10On Tue, May 01, 2012 at 08:38:00AM -0700, Father Chrysostomos via RT wrote:
Well, IIRC from the part you trimmed, the questions were about documentation The original reported problem in the script is that it's tripping up on a That's not really a perl interpreter behaviour bug. Nicholas Clark |
Migrated from rt.perl.org#17711 (status was 'resolved')
Searchable as RT17711$
The text was updated successfully, but these errors were encountered: