problem with running "kill -QUIT 1" from init
Rob Landley
rob at landley.net
Tue Jan 27 02:14:30 UTC 2009
On Thursday 22 January 2009 22:55:23 Aras Vaichas wrote:
> One extra note, I do some trickery with /etc/inittab.
>
> # cat inittab.new
>
> ::restart:./upgrade_nand
>
> I change the existing inittab to run my upgrade script, tell init to
> reload the new, and then restore the old one so I can continue testing.
>
> # cp /etc/inittab inittab.bak
> # cp inittab.new /etc/inittab
> # kill -1 1
> # cp inittab.bak /etc/inittab
>
> It seems that doing "kill -1 1" from /etc/init/rcS doesn't reload the
> inittab.
The busybox init is a bit of a hack.
I made a largeish stab at cleaning it up during the 1.0.0-pre timeframe, but
the source control system was frozen for several months (during the switchover
from cvs to svn) so I couldn't check it in, and by the time it was unfrozen
I'd had a laptop destroyed and lost the code. Never got back around to
redoing it.
The current maintainer has chosen instead to implement a different group of
init-like programs (sv, runsv, runsvdir and friends, the "runit" package),
which can best be described as "not compatible with Ubuntu's upstart". That's
what he pays attention to, not the original sysv-like init.
So my vague impression is that the init implementation in busybox has largely
been ignored for some time now...
Rob
More information about the busybox
mailing list