[BusyBox] Init does not always reap child processes

[Rob Landley]

On Friday 29 July 2005 11:02, Jason Schoon wrote:
> I agree, it's a weird scenario.
>
> We actually want init to wait, because the one action following the
> wait call is a call to reboot.  Essentially, if anything goes wrong or
> causes the main app to exit, we want the thing to reboot.

It sounds like what you want to do is run with init=/your/app and
echo 1 > /proc/sys/kernel/panic

That way if your app exits, that counts as init exiting and panics the system, 
which gets translated into a reboot after 1 second.

> This is an 
> embedded system, and in production mode we don't want them
> unceremoniously ending up at a shell prompt.

What kind of interface?  (The last system I set something like this up for was 
a network attached device that did all configuration through a web CGI 
thing.)

Rob