The latest dcron version can handle @something. With the usage of @someting some cron daemons can do the same thing as anacron. They check if the told cronjob was running in the given period or not and start it when necessary.
This is a feature of the new dcron to. But he needs an ID=<jobid> added als ENV variable to the cron command. :-( In the next version this should be fixed. -- crontab syntax invalid with some cron daemons https://bugs.launchpad.net/bugs/409783 You received this bug notification because you are a member of Back In Time Team, which is subscribed to Back In Time. Status in Back In Time: Fix Committed Bug description: When a cron schedule is created, at the moment the application creates a crontab entry using the @ prefixed shorthand syntax (eg @daily) instead of traditional syntax (eg, 0 1 * * *) Not all cron daemons recognise this syntax so the schedule never runs - dcron for example. This is further complicated by the over zealous removal of crontab entries when the settings dialogue is opened/closed which deletes manually created entries with valid syntax. _______________________________________________ Mailing list: https://launchpad.net/~bit-team Post to : [email protected] Unsubscribe : https://launchpad.net/~bit-team More help : https://help.launchpad.net/ListHelp
