o re-write it to
trap a signal (e.g. SIGUSR1) that instructs the child to kill /its/
child (the assumption being that the child knows its own child's
PID).
This is not a bad idea. I may explore this in a future rev...
--
Jim Seymour
--
Unsubscribe info: http://cygwin.com/ml/#uns
Gary Johnson wrote:
From a shell prompt, execute
cygcheck -p killall
Thanks. Found it in the psmisc package.
Now, I have a program that works as I expect without too much
line-noise-as-syntax... :-)
--
Jim Seymour
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Lev Bishop wrote:
On 10/23/06, Jim Seymour <[EMAIL PROTECTED]> wrote:
However, if things don't work fine, the background process sticks around
to plague me later.
I'd like to end my main script by killing the background process (if
it's still around), but I'm havi
6 con 11024 17:00:39 /usr/bin/sh
3340 724 7243048 con 11024 17:00:41 /usr/local/bin/ocdremote
3556 2196 3556 2192 con 11024 17:00:49 /usr/bin/ps
$ kill %?ocdremote
bash: kill: %?ocdremote: no such job
--
Jim Seymour
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
4 matches
Mail list logo