The following change should address this bug: --- /etc/cron.d/anacron.orig 2010-06-20 04:11:29.000000000 -0400 +++ /etc/cron.d/anacron 2012-01-06 18:03:48.000000000 -0500 @@ -4,4 +4,4 @@ PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin #30 7 * * * root test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null -30 7 * * * root start -q anacron || : +30 7 * * * root start --quiet anacron 2>/dev/null || :
The cron-job command is written to disregard failure of the start(8) command, but it was not absorbing the error message that would be produced in such an instance. (I also changed -q to --quiet, as the former is not documented in the initctl(8) man page.) Of course, this does nothing for the apt bug that appears to be associated with this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606491 Title: start: Job is already running: anacron To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/606491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
