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
On Wed, Aug 24, 2016 at 12:08 PM, Peter Korsgaard wrote:
> The udhcpc script may be used to setup fallback configuration (E.G. IPv4LL,
> fixed IP address, ..) that also needs to be cleaned up on release (E.G.
> when SIGUSR2 is called or on shutdown with -R), so
The udhcpc script may be used to setup fallback configuration (E.G. IPv4LL,
fixed IP address, ..) that also needs to be cleaned up on release (E.G.
when SIGUSR2 is called or on shutdown with -R), so unconditionally call
deconfig.
Signed-off-by: Peter Korsgaard
---