Comment 9 for bug 606491

Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

Got another email this morning. Here's the relevant lines from
/var/log/syslog showing the overlap between the first anacron and the
second started by cron.

    Apr 16 07:29:40 orac cron[1097]: (CRON) INFO (pidfile fd = 3)
    Apr 16 07:29:40 orac anacron[1111]: Anacron 2.3 started on 2011-04-16
    Apr 16 07:29:40 orac cron[1159]: (CRON) STARTUP (fork ok)
    Apr 16 07:29:40 orac anacron[1111]: Will run job `cron.daily' in 125 min.
    Apr 16 07:29:40 orac anacron[1111]: Will run job `cron.weekly' in 130 min.
    Apr 16 07:29:40 orac anacron[1111]: Jobs will be executed sequentially
    Apr 16 07:29:41 orac cron[1159]: (CRON) INFO (Running @reboot jobs)
    Apr 16 07:30:01 orac CRON[1554]: (root) CMD (start -q anacron || :)
    Apr 16 08:17:01 orac CRON[2917]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
    Apr 16 09:17:01 orac CRON[6188]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
    Apr 16 09:34:40 orac anacron[1111]: Job `cron.daily' started
    Apr 16 09:34:40 orac anacron[7716]: Updated timestamp for job `cron.daily' to 2011-04-16

My longer initial delays for anacron show up the issue more by
increasing the window that it can occur in, but it's there with the
default delays too.