[Bug 554172] Re: system services not starting at boot

[Andy Whitcroft]

Having talked to upstream and clarified the plans with the BTM, it
seems that they are intending on closing some of the races as they are
deemed unhelpful.  Overall however some slow TTY devices will indeed
still legitimatly return EIO when a slow close is in operation.  That is
expected behaviour.

Looking at upstart it does appear that a change there has exposed us to
this issue.  Until recently upstart used to hold /dev/console open in its
own name.  That was stopped (quite reasonably) to avoid another issue,
from the changelog:

    0.6.5 2010-02-04 "Our last, best hope for victory"
    [...]
     * No longer holds /dev/console open, so the SAK SysRq key will not
       kill Upstart. (Bug: #486005)
    [...]

If we look at upstart itself, it seems to be using a plain open which
likely should be more robust in any case:

    system_setup_console (ConsoleType type,
    [...]
	    switch (type) {
	    case CONSOLE_OUTPUT:
	    case CONSOLE_OWNER:
		    /* Ordinary console input and output */
		    fd = open (CONSOLE, O_RDWR | O_NOCTTY);
		    if (fd < 0)
			    nih_return_system_error (-1);
    [...]

-- 
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.