-
Notifications
You must be signed in to change notification settings - Fork 561
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
qx seems to loose the subpr. way for print /dev/tty #8374
Comments
From ende@telefonica.netCreated by juanfc@lcc.uma.esI send messages through /dev/tty with exec echo >/dev/tty in a tcl script that is called from a Perl script. The Perl script is on forever with a loop, allowing me In the "daemonized" perl script, that has the loop: while (1) { only the first time the Tcl program is runned, the messages sent If I do the same stuff with sh while [ 1 -eq 1 ]; do there is no problem at all. Perl Info
|
From @rgarciaOn 3/17/06, via RT ende <perlbug-followup@perl.org> wrote:
What happens if you use system() instead of `` ? system doesn't
|
The RT System itself - Status changed from 'new' to 'open' |
From shouldbedomo@mac.comOn 2006â??03â??17, at 09:40, ende (via RT) wrote:
Can you make a short script (or pair of scripts) in pure Perl that $ perl -MPOSIX=setsid -lwe 'unless (fork) {setsid; qx(tty > /dev/ and the same on PPC Linux: $ perl -MPOSIX=setsid -lwe 'unless (fork) {setsid; qx(tty > /dev/ (In both cases, we are seeing a complaint sent by the shell to |
From ende@telefonica.net#!/usr/local/bin/perl while (1) { sleep 600; # END # #################### eval [list exec echo >/dev/tty " -->> \[$cola\] [string range # #################### # this script calls programs that could use stdout # The first time the script is called the echo > /dev/tty works but, #!/bin/bash while [ 1 -eq 1 ]; do sleep 600 # all goes well, no problem. bash does not interfere with the output of El 17/03/2006, a las 16:05, Dominic Dunlop via RT escribió:
|
From @dcollinsnThis ticket badly needs to be reviewed by a Darwin expert. Is there something that we need to work around on this OS? (Can you summarize it and update the ticket name?) -- |
From [Unknown Contact. See original ticket]This ticket badly needs to be reviewed by a Darwin expert. Is there something that we need to work around on this OS? (Can you summarize it and update the ticket name?) -- |
@dcollinsn - Status changed from 'open' to 'stalled' |
From @arcDan Collins via RT <perlbug-comment@perl.org> wrote:
I've tried and failed to reproduce this: $ uname -sr It seems to me that whatever bug existed when this ticket was filed a -- |
From @dcollinsnOn Tue Jul 12 10:18:05 2016, arc wrote:
Thank you, Aaron. Taking with the intent to close in 7 days unless there is anyone who can provide a test case that we can reproduce. -- |
The RT System itself - Status changed from 'stalled' to 'open' |
I think this case was not closed by mistake. Closing it now. |
Migrated from rt.perl.org#38748 (status was 'open')
Searchable as RT38748$
The text was updated successfully, but these errors were encountered: