*** This bug is a duplicate of bug 27520 ***
https://bugs.launchpad.net/bugs/27520
** This bug has been marked a duplicate of bug 27520
cron daemon starts before LDAP/NIS client, causing "ORPHAN" message for all
LDAP/NIS-defined users
--
You received this bug notification because you are
At a glance I would say that your issue and mine aren't related. This
bug is the exact same issue I filed before, only instead of the init
script firing after cron has started, upstart is starting likewise after
cron has started. Same bug, different thing futzing up the launch
order.
--
reboot
I have similar problem but with ALL cron jobs (my user's jobs).
First I schedule a job to run daily at certain time, I reboot, log-in before
the job start time and cron ignore the job completely (nothing logged in syslog)
Then I schedule another job (exactly same as above), reboot, log-in, but now
