Am 18.06.2011 03:19, schrieb Christian Kastner: > 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.
I understand that. I've been trying to point out that the libc getpw*() interfaces have no means to reliably/portably return error conditions to distinguish between "temporary issue" and "user not present", and nsswitch can't help here either. (a. it doesn't properly map "NIS domain not bound yet" to a temporary condition, b. even if it did there were no means to make it retry). My conclusion is that cron needs to check for user existence with getpwnam() or similar each and every time it tries to *run a job*, not just when reading the crontabs. -- Matthias Andree -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
