🚀 go-pugleaf

Thanks to Michael Cook <mcook@merlin.dev.cdx.mot.com>, I know the answer to
my question. 

Summary of the problem:
A signal is sent to a shell script with process id 12345 and job number 1 (in
csh) that is currently executing a sleep command.
The signal USR1 seems not to arrive when sent with the command:

kill -30 12345

It does arrive, however, when sent with

kill -30 %1

How is this possible, and how can I interrupt the script in case the job number
is not accessible and I don't want to signal the sleep process explicitly?

The answer is that the first command sends a signal to the script process
*only*, whereas the second sends it to the process *group* (all processes
dependent on 12345).  As long as the sleep is executing, the shell script
process is suspended and buffers the incoming signals. And the intention was
abort the sleep process and ahndle the signal immediately.

Solution: use 

kill -30 -12345

This to me unknown (SysV?) feature of the kill command sends the signal to
every member of the process group. It works on my Sun. 

Thanks to everyone who thought about this, especially to Michael.
Kees

-- 
Kees Huizing - Eindhoven Univ of Techn - Dept Math & Comp Sc - The Netherlands
e-mail: keesh@win.tue.nl   telephone: +31-40-474120    fax: +31-40-463992