[BusyBox] Can init reread inittab? Not really....? Ur...p.

[Tom Oehser]

Also, when I do setup a ::restart: entry, it only seems to work once ???

That is strange...

I put ::restart:/sbin/init, and the first time I 'init -q' or 'HUP', it
runs... but then, not again.

I guess I can play games with writing status flags to the filesystem to
make it know the difference between when init starts and when init
reloads... if I can get it working consistently.

-Tom

On Tue, 23 Apr 2002, Tom Oehser wrote:

> Date: Tue, 23 Apr 2002 16:40:03 -0400 (EDT)
> From: Tom Oehser <tom at toms.net>
> To: Giulio Orsero <giulioo at pobox.com>
> Cc: andersen at codepoet.org, busybox at busybox.net
> Subject: Re: [BusyBox] Can init reread inittab?   Not really....?  Ur...p.
>
>
> I see in the archives:
>
> ...
> > But this way everything is restarted and re-run, rc.sysinit is re-executed
> > and tries to re-setup the system. If I take out "::restart..." line, then it
> > seems nothing happens (ie: I delete the tty4 line, init -q, kill the tty4
> > getty, and it's restarted). I looked at "static void exec_signal(int sig)"
> > and it seems it does something only if it has to "restart".
> ...
>
> I guess this was deemed "not a bug"?  If I want it to behave more like
> sysvinit maybe I'm on my own?  What I want is that -q or HUP will:
>
> -Not restart
> -Re-read the inittab
> -Act on new entries
> -Kill deleted entries
> -Ignore unchanged entries
>
> Which is something like what sysvinit does.
>
> As it is, all you can do is completely restart everything, which in my case
> would make an endless loop...
>
> -Tom
>
>
>
>
>
>
>
>
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
>