Carlos E. R. wrote:
The Sunday 2005-11-06 at 14:35 +0100, Joachim Schrod wrote:
I confirmed that behavior for 9.1 and 10.0. Is that `works as intended', or is that a bug?
I think the former. From man 8 cron:
Additionally, cron checks each minute to see if its spool directory's mod time (or the modtime on /etc/crontab) has changed, and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Yeah, I checked the man page, too. But I don't think that the paragraph above is concerned with /etc/cron.d at all -- it tells only about the spool files (in /var/spool/cron/tabs that are managed by crontab(1)) and /etc/crontab. I was not successful in finding any documentation about the supposed behavior of /etc/cron.d files at all. And if the intention is that `cron need not be restarted whenever a crontab file is modified', that intention is not successfully implemented for cron.d entries. Or do I miss something that's significant in the paragraph above? Please advise. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany