Re: open (to read) and kill a pipe to a pipe

Replies are listed 'Best First'.
Re^2: open (to read) and kill a pipe to a pipe by darist (Initiate) on Aug 26, 2010 at 22:14 UTC
Thanks Your Mother! `kill 9, -$pid; # didn't work # But... kill -9, $pid # WORKS !!!` [download] From perldoc on kill: if SIGNAL is negative, it kills process groups instead of processes. That means you usually want to use positive not negative signals.	[reply] [d/l]
Re^3: open (to read) and kill a pipe to a pipe by ikegami (Patriarch) on Aug 26, 2010 at 22:51 UTC
That's interesting since Windows doesn't have process groups. I wonder what it actually does ( when asked to kill a process group ).	[reply]
Re^4: open (to read) and kill a pipe to a pipe by BrowserUk (Patriarch) on Aug 27, 2010 at 18:27 UTC
See `kill_process_tree_toolhelp()` in win32.c	[reply] [d/l]
Re^4: open (to read) and kill a pipe to a pipe by rowdog (Curate) on Aug 27, 2010 at 15:34 UTC
Corion recently told me that "under the Windows fork emulation, emulated forked children get negative PIDs". I don't know where this is documented but I believe him.	[reply]
Re^5: open (to read) and kill a pipe to a pipe by ikegami (Patriarch) on Aug 27, 2010 at 16:46 UTC
Re^6: open (to read) and kill a pipe to a pipe by rowdog (Curate) on Aug 27, 2010 at 17:14 UTC
Some notes below your chosen depth have not been shown here
Re^2: open (to read) and kill a pipe to a pipe by ikegami (Patriarch) on Aug 26, 2010 at 22:49 UTC
~~You said ActivePerl and Windows, but `system("thingy &")` doesn't work on Windows. ("`&`" is like `sh`'s "`&&`".)~~ Mixed YourMother's post and the OP's	[reply] [d/l] [select]