Yeah I thought it might be by design but in this fairly old busybox, 1.22.1, it doesnt seem to be the case, since it never got repeaed the processes hanged on and had control over the service subdirs until being killed with SIGTERM from the shell, so might bw that init is broken in this version.
Thanks for letting me understand the rationale of this. //M Skickad via BlackBerry Hub för Android Ursprungligt meddelande Från: ska-dietl...@skarnet.org Skickat: 23 december 2017 09:21 Till: busybox@busybox.net Svara till: ska-dietl...@skarnet.org Ämne: Re: Question regarding runsvdir not reaping children. >What is the rationale behind not reaping the children when the program >exists? i run it from inittab as a respawn process and I get zombies >when killing it when not reaping children alas the fix was pretty >simple. Unless you're running runsvdir as process 1, there's no reason to do so, because on runsvdir's death, its children will be reassigned to init, and init will reap those zombies. If you're getting zombies when killing runsvdir, then you have another problem, that is unrelated to runsvdir. Note that busybox init sometimes takes one second to reap zombies (which is what you may have observed). This is a flaw in the design and cannot be fixed without significantly rewriting it, but it should not matter for practical purposes - zombies hanging around for one second is generally not an issue. -- Laurent _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
