I see that LP: #605123 describes a similar situation when cron is started before the likewise-open daemons, while the Debian BTS 512757 mentioned above relates to NIS users, etc.
And even if the startup script order is fixed in all these cases, its always possible that the LDAP (or whatever) server will be unreachable when a particular machine is started, which presumably could result in the same ORPHANing process happening for cron session.... All of which makes me think that perhaps Stephane Chazelas's idea (comment #10) about having cron check the validity of the user continually, rather than only at startup, makes more sense in modern network-based environments.... -- 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 starts before LDAP client, causing "ORPHAN" message for all LDAP-defined users -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
