inittab: Start shell only if console is not null

[Harald Becker]

Hi Denys!

>
>>> If that open fails, then respawning will not be done.
>>
>> Actually I'm testing this and it seems that init keeps spawning child
>> processes forever, every second. Inside run(), vfork succeds but then
>> the device open fails and the child process _exits().
>>
>> Is there a way to have init completely skip the line if the
>> controlling tty is not valid or cannot be opened.
>
> May be we can disable the inittab entry, when the spawn fail (e.g. 
> process status code -1 or 127), until init get a SIGHUP (reload inittab)?

I suggest doing something like the attached patch (this is just for 
clarification - not fully tested).

--
Harald

-------------- next part --------------
A non-text attachment was scrubbed...
Name: init.patch
Type: text/x-patch
Size: 2559 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20140828/30cdbcc8/attachment.bin>