On 06/07/2011 06:13 PM, Matthias Andree wrote: > Note that while the trigger is cron starting before the respective user > database (NIS, LDAP, whatever), cron should really re-check each time to > be resilient to temporary network hicc-ups.
In general, cron does not contain a single line of networking code, temporary network hiccups really aren't its problem. Please don't take this wrong, I'm merely trying to point the difficulties I face as a Maintainer. In this particular case, though, temporary hiccups would only matter if a crontab were to be changed and saved during such a hiccup, so the risk is only minor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/27520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
