Note there may be two separate fixes involved here (for Lucid, at least; not sure about Maverick)
In the short term, how can we once-again tweak the startup scripts so that cron is always started after nslcd/nis/likewise-open/whatever has already started (especially if the other damon in question is still using a /etc/init.d/-style startup script? In the longer term, obviously it would be great for cron better integrate with network-based user databases, but it would be nice to hear from some Ubuntu developers whether that sort of change is likely to get backported to Lucid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/27520 Title: cron daemon caches user-non-existent lookup results, causing "ORPHAN" message and skipping jobs for all LDAP/NIS-defined users -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
