Joel, Till Re comment #122. I believe you have it backwards.
I believe if you apply the get-around spelled out in comment #83 of http://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506 you will find that your CUPS starts will be reliable. I've seen native 10.4 upstart boot go to "unknown" after many boots to "N 2" and vice versa. By applying the get-around from comment #83, my boots became 100% reliable; 100% "N 2". Till, Re comment #123. I believe that is exactly right. The Upstart infrastructure seems to be inherently unstable because there is no fixed order of startup scripts. Just because it boots once correctly to runlevel "N 2" you cannot assume that it won't boot to runlevel "unknown" sometime in the future. This is because the order of /etc/init/*.conf and /etc/rc2.d/S* scripts are run is not fixed. -- CUPS and other system services not starting at boot https://bugs.launchpad.net/bugs/554172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
