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

List:       busybox
Subject:    Re: [PATCH] udhcpc: perform_release(): Unconditionally call deconfig script
From:       Laurent Bercot <ska-dietlibc () skarnet ! org>
Date:       2016-08-26 17:00:51
Message-ID: 02901552-d0fe-6252-aa1d-a8b66ce625b0 () skarnet ! org
[Download RAW message or body]

On 26/08/2016 18:53, Denys Vlasenko wrote:
> However, a more robust solution is to have process babysitter
> to run some cleanup script. Imagine that udhcpc is killed with SIGKILL.
> Can't handle that easily inside udhcpc...

  Does the cleanup script need to be run every time udhcpc dies?
A process supervisor can run a finish script that knows the exit code of
udhcpc, or the signal that killed it, but if there are moments when you
_don't_ want to run the cleanup script if udhcpc receives a SIGKILL, then
it's more complicated. A supervisor can only know how the service died,
it cannot know the state the service was in when it got killed.

-- 
  Laurent

_______________________________________________
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]