We now have the functionality that anacron runs on power status change.
It might still be worthwhile to implement a configuration setting that
makes anacron always run whether on AC power or not, but I think the
severity of this problem is now much lower. Basically, you will only be
affected if
I think anacron (and the same for corn, at) should always be started,
regardless of AC or not.
It's the duty of the respective cron-job to determine, whether the sys
is on battery and whether the job is so important to have it run anyway.
Apart from that, I cannot believe that this severe
tag 426294 +patch
thanks
I think the core of the problem is the cron entry in
/etc/cron.d/anacron. It only runs anacron once a day, which completely
defeats the purpose of anacron (which was to be able to run daily jobs
even for machines which are turned off most of the day).
It might be OK for
anacron deliberately doesn't run if the machine is running on battery
power. This is fine if the only jobs are housekeeping tasks that
it's safe to skip, but if you have critical jobs like backups then it's
not so good. This is a dangerous situation as users are unlikely to
notice that this
Package: anacron
Version: 2.3-13
Severity: normal
Hello,
i can see that anacron is not started at boottime if /usr/bin/on_ac_power.
Then it tries to start everyday in /etc/cron.d/anacron at 07H30.
This totally fails. I have just realized that my crontab hasn't been
run for 1 month. So either
5 matches
Mail list logo
