The feature you are describing is the exact purpose of anacron. Could you elaborate what you mean by "hasn't the precision of cron"? What can cron do that you can't do with /etc/anacrontab?
BTW, it doesn't make sense for anacron to be a full-time daemon, because when the system is up, you already have the cron daemon executing your jobs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1280808 Title: Support for afterwards execution of missing jobs Status in “cron” package in Ubuntu: New Bug description: I'm using Ubuntu 14.04 dev with cron 3.0pl1-124ubuntu2 and maybe cron can get the ability to run missing jobs on booting like anacron. The question why I'm not using anacron: It has limitations as it is not a full time deamon and hasn't the precision of cron. For example if I'm defining a job to run every day at 02:30 but the computer gets a power loss at 2:29 and is online at 2:31 it would be nice if cron does calculate on startup if there were jobs that had to be executed. For this case cron needs to store the last execution time of a job and an extra column on the job entry as option list to en-/disable this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1280808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp