On Thu, Aug 28, 2014 at 3:48 PM, Harald Becker <[email protected]> wrote: >> What if /dev/FOO does not exist YET? (E.g. USB-based serial TTY). >> What if execve fails because /usr/bin/BAR does not exist YET? > > Both cases can be solved when startup code send a SIGHUP to init when all > this stuff is available (at end of rc scripts do kill -SIGHUP 1) > > Not to talk about: Normal respawning actions are started when sysinit > actions has finished. All required devices and file systems shall be online > at this time and so respawn actions will not get affected. > >> What if some people who use bbox init expect respawn to retry until >> success in these cases? > > > What about all those people who can't use Busybox init due to its endless > and relatively fast respawning (wasting process id's).
I imagine we would have these people complaining on the mailing list by now. > Your argument here is confusing. Do you really look for people using bbox > init due to it's long standing bug of endless respawning unavailable > services? My argument is that before adding code, it makes sense to ponder whether we really have a real problem here. If one respawn per second a big problem? I'm not sure. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
