SIGTERM is not killing udhcpc
Bryan Evenson
bevenson at melinkcorp.com
Wed May 21 19:40:15 UTC 2014
Laurent,
> -----Original Message-----
> From: busybox-bounces at busybox.net [mailto:busybox-
> bounces at busybox.net] On Behalf Of Laurent Bercot
> Sent: Wednesday, May 21, 2014 3:00 PM
> To: busybox at busybox.net
> Subject: Re: SIGTERM is not killing udhcpc
>
>
> > On my system I modified networking/ifupdown.c to call "kill -9" instead of
> "kill" to kill udhcpc (lines 539 and 617) and now udhcpc stops as expected
> when I bring the related interface down. However, I've been through
> networking/udhcp/dhcpc.c and I don't see any obvious reason why it won't
> respond to a standard kill command. Anyone see a reason why this would
> happen?
>
> Can you please strace udhcpc, then send it a SIGTERM, and post the output
> of the strace ? It will show where udhcpc is blocking after receiving the signal.
>
Of course now I can't reproduce the problem. On my system the only thing that I changed with Busybox was adding "kill -9" to ifdown, which doesn't change any of the udhcpc code but a standard kill will now bring down udhcpc. I have a separate machine that was running the same version of Busybox before my patch and SIGTERM kills udhcpc on that machine. The only time I was able to produce the problem is on a machine that no longer exhibits the problem.
Unless I can reproduce the problem I'm going to assume that there was some unreproducible oddity with my machine that has now been fixed by reinstalling Busybox. Sorry for the noise.
Bryan
> --
> Laurent
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
More information about the busybox
mailing list