RoyK, its been difficult to work on this as its not clear how to reproduce yet. I'm wondering if this has to do with alternative user/group sources like ldap and such. runlevel 2 happens before the network is up, so calls to getent() for users that don't exist might cause a failure. This would affect systems using winbind, NIS, etc. etc.
Can somebody who is affected try changing /etc/init/cron.conf's start on line to be start on net-device-up IFACE!=lo to confirm that? Also it may help to just move the start on line to after all sysvinit jobs.. start on stopped rc RUNLEVEL=[2345] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592114 Title: upstart doesn't start cron automatically on boot in lucid for server on amd64 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
