-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDblqZtTMYHG2NR9URAhgTAJ48jKIRPrAcFkQ2C/UH5Hw8Qga4JQCgmJ0H WQQXS/YaKLArvulBzoSY0X0= =a2M2 -----END PGP SIGNATURE-----