'kill 0' from cron script kills crond
Jeroen van der Vegt
jeroen.van.der.vegt at technolution.nl
Tue Dec 2 16:40:06 UTC 2008
Hello,
We're using Busybox on an embedded ARM platform. We'd like to have a script
running from cron every minute. To terminate any remaining child processes,
we'd like to perform the 'kill 0' command at the end of the script. This '0'
is a special argument. From e.g.
http://linux.about.com/od/commands/l/blcmdl1_kill.htm :
.....
0
All processes in the current process group are signalled.
....
It seems that this command works in Busybox as well. However, if we use this
in a script that is run from 'crond', crond itself is killed as well. That
is obviously not as expected, and indeed different from the behaviour of a
system without Busybox.
I found this behaviour with version 1.4.1, but it was easily reproducible
with version 1.10.2 from the Debian archives.
Is this the expected behaviour? If so, what command can we issue to kill all
child processes?
Regards,
Jeroen van der Vegt
System designer
________________________________
Technolution B.V.
Telephone: +31(0)182 59 40 00
Fax: +31(0)182 53 97 36
E-mail: Jeroen.van.der.Vegt at technolution.eu
Visit us at: www.technolution.eu Mailing address: P.O. Box 2013 - 2800
BD Gouda - The Netherlands
Address: Zuidelijk Halfrond 1 - 2801 DD Gouda - The Netherlands
________________________________
This e-mail is intended exclusively for the addressee(s), and may not be
passed on to, or made available for use by any person other than the
addressee(s). Technolution B.V. rules out any and every liability resulting
from any electronic transmission.
More information about the busybox
mailing list