Harald Küthe wrote: > Our inittab calls a startscript which is not ended during runtime, but > only when the settopbox shuts down. > I would consider this an application error and not a problem of init.
> There exists a patch which is hanging around in our development tree for > ages now which we used to avoid zombie processes. > This is maybe related to some old stuff found here: > http://www.busybox.net/lists/busybox/2004-August/012422.html > This patch will solve your zombie problem, but it will only work because you don't use any other of init's functions. init will loop in waitfor(), waiting for your start script to stop, which it will not. The only difference is that with the patch init will wait for other processes. But init will not start any other processes that should run from inittab. This is probably not important for you because you don't have other actions in inittab. But the solution to your problem is not to patch init but to run you "start" script in the background or to use "once" instead of "sysinit" in your inittab. "once" actions are started by init, but init doesn't wait for them. Personally, I prefer to see the zombie processes as a strong indication for a problem with the start script to an init that doesn't run processes without any hint. Regards Ralf Friedl _______________________________________________ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
