The bug as reported in Bug #554172 is definitely not fixed!
The workaround to direct output to /dev/null if console is not available
is just a fake. Or would you leave users with a black screen in case
X-server does not start?
The result is - besides some services not starting reliable - that
randomly a lot of boot messages get lost. Can be easily seen, if
plymouth has been purged to display boot messages. This definitely is a
bug in upstart, as upstart claims to start services whenever all
prerequisites are met.
So instead of just dumping the output, upstart should wait for the
console to be available.
In Bug #554172 it is stated to be a kernel-bug, where can I follow the
kernel-bug, or is it rather a known feature of the kernel in case of
SMP-systems?
** Changed in: ubuntu
Status: New => Confirmed
--
Services not starting on boot in 10.04.1 LTS
https://bugs.launchpad.net/bugs/642555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
