[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [patch] option -k of ifplugd did not work
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2013-02-28 11:53:13
Message-ID: CAK1hOcPbqiryDOzp0pO8y-T7H2WtQXSNcxQe-T9RWqMnriBrfQ () mail ! gmail ! com
[Download RAW message or body]

On Fri, Dec 14, 2012 at 10:39 PM, Matthias Loy <matthias.loy@hbm.com> wrote:
> Hello,
>
> today I reconized that ifplugd -k does stop the running ifplugd without
> calling ifdown. Sending SIGTERM to the ifplugd did the job, ifdown was
> called before ifplugd stopped.
> The solution is simple: ifplugd -k sent the wrong signal. the clean up stage
> was simply omitted!
>
> Attached is the small patch solving the problem.

I looked at upstream sources and they send SIGINT.
I changed bbox code to do the same.

Thanks!

> By the way. A few weeks ago I send another patch concerning ifdown for
> interfaces using a mapped configuration. Until now I haven't got any
> reaction from anybody.

Sorry. I will take a look.
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]