tags 315714 + confirmed
thanks
* Sven Joachim ([EMAIL PROTECTED]) disait :
> In version 0.5.7.1 of backup-manager, the cron script was moved from
> /etc/cron.daily to /etc/cron.d. This has a rather undesirable side effect
> for
> people who don't keep their system running continuously. Those people (like
> me)
> usually have the anacron package installed to take care that maintenance
> tasks
> are executed. Alas, anacron only looks for scripts in
> /etc/cron.{daily,weekly,monthly}, but not in /etc/cron.d.
Indeed. I recently noticed that too. The choose of cron.d was made in
order to provide an easy way to change the frequency (see #300798).
That's indeed a real problem anacron does not handle cron.d files...
> IMHO, this also violates the policy: quoting from section 9.5 of the Debian
> Policy
>
> [...]
>
> And two paragraphs later, the Policy Manual states:
>
> If a certain job has to be executed more frequently than daily, the
> package should install a file `/etc/cron.d/<package>'.[...]
> Note that entries in the `/etc/cron.d' directory are not handled by
> `anacron'. Thus, you should only use this directory for jobs which
> may be skipped if the system is not running.
Hmm, thanks for having pointing your finger on that part, I really
wasn't aware of such a violation.
My problem is to find a way to close this bug without reopening #300798.
> As backup-manager is to be run at most once per day, it should not put a
> script in /etc/cron.d. So, the lesser evil may be to restore the old
> behaviour of placing a script in cron.daily.
Indeed, but I have to keep attention on giving a way to choose another
frequency as well, that's the tricky point.
I'm working on it...
Thanks for the report.
Regards.
--
- Alexis Sukrieh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
