[BusyBox] job control turned off, yet again aganin and again

Rob Landley rob at landley.net
Wed Sep 15 07:02:24 UTC 2004


On Tuesday 14 September 2004 02:42, Vladimir N. Oleynik wrote:
> Jeff,
>
> > Now I got this to work as long as I had all of the respawn lines
> > commented out.  And I notice that you use once for your inetd action.
>
> It is very old discussion. In the present UNIX system the "init"
> does not allow controling terminal for respawn sessions.
> "init" make steal controling terminal from exited session only.
> Set controling terminal is given with "getty".
>
> But modern users do not want to accept such behaviour
> and on it specificity of "busybox" usage is imposed:
> use in the minimalistic systems.
>
>
> --w
> vodz

I still have trouble understanding what you're saying, but stealing the 
controllig terminal back from exited sessions is something I ripped out of 
the new init I'm writing.  (We can grab the controlling terminal when we 
spawn the session, so why do we need to take it away arbitrarily from an 
ended session?  What if it had child processes that still want it?  What if 
it was a TTY that nothing else is on?  What does stealing away the tty on 
exit accomplish?  I keep meaning to ask about this, but don't know where...)

Rob
-- 
www.linucon.org: Linux Expo and Science Fiction Convention
October 8-10, 2004 in Austin Texas.  (I'm the con chair.)




More information about the busybox mailing list