On 14/11/2011, at 7:54 PM, Christian Kastner wrote:
On 2011-11-13 01:29, Michael Tomkins wrote:
Package: cron
Version: 3.0pl1-120
Severity: important
Dear Maintainer,
* What led up to the situation?
Noticed that weekly Analog run via cron.weekly was about 4 weeks
old. This was prior to a apt-get upgrade. Upgrade broke something.
anacron hasn't changed in ages, and the last cron upload was 2 months
ago, so at the moment, I have no idea what could have gone wrong.
Still possibly within timeframe. I do apt-get upgrade infrequently,
the change could be within the last 3 months.
the analog script has perms
-rwxr-xr-x 1 root root 63 Sep 25 10:35 analog
$ cat /etc/cron.weekly/analog
#! /bin/sh
test -x analog || exit 1
nice -10 analog
exit 0
What do the log files say? Did other (non-anacron) jobs run
successfully)? Are there any failure messages for anacron?
I have an IP logging script in daily that is running. HMMM.
Checked anacron and looked at logic. Anacron appears to remove itself
from running processes after running once.
This is by design. anacron is not a daemon, it is supposed to be
started
by cron.
Ok.
Cron checks for anacron and if executable then doesn't run daily,
weekly or monthly. But anacron is not resident and only runs when
daily, weekly or monthly cron runs. This circular logic means that
daily, weekly or monthly will never run.
You are overlooking the script anacron installs to /etc/cron.d. It is
run on a daily basis, which means that all the jobs that cron is
skipping in /etc/cron.{daily,weekly,monthly} are executed by anacron.
Then downgrade this bug as that covers standard running logic so
it's probably in my script or setup.
Christian
--
Michael Tomkins
mic...@gmail.com
+61 408 172 142
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
