We 're also running into this in Lucid -- each (or at least most) times we reboot, we see messages like this in our syslog (with messages generated by other applications removed):
May 6 22:59:26 vm-76 cron[606]: (CRON) INFO (pidfile fd = 3) May 6 22:59:26 vm-76 cron[617]: (CRON) STARTUP (fork ok) May 6 22:59:26 vm-76 cron[617]: (LdapUser) ORPHAN (no passwd entry) May 6 22:59:26 vm-76 cron[617]: (CRON) INFO (Running @reboot jobs) May 6 22:59:28 vm-76 nslcd[968]: version 0.7.2 starting May 6 22:59:28 vm-76 nslcd[968]: accepting connections May 6 22:59:30 vm-76 nslcd[968]: [8b4567] connected to LDAP server ldap://ldap.... The "LdapUser"'s crontab is then disabled until we do a "restart cron" (or, presumably, the user does a "crontab -e" to touch his/her crontab file). (/etc/nsswitch.conf contains the line "passwd: compat ldap", and the "libnss-ldapd" package is installed.) Unfortunately, in Lucid cron had been switched to an Upstart job, but nslcd is still using an rc.d script, so I am not sure the proper way to ensure that nslcd is started before the cron daemon.... -- 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
