tag 627859 + pending thanks On 05/25/2011 01:44 AM, Axel Beckert wrote: >>> Now fix the missing newline in test1 by adding it again. It still won't >>> run the cronjobs in there until you either: >>> >>> * Edit _another_ file in /etc/cron.d/, e.g. test2 >> >> Hm, this one is strange. > > I also checked with "ls -li" that overwriting a file with ">" does not > remove the old file and create a new one in my shell (zsh), but really > just overwrites the file, i.e. the inode number does not change and > the directory's mtime does not change either.
It isn't strange after all, I just overlooked the "overwriting" part. Without the directory's mtime changing, we're back to the previously mentioned scanning algorithm. >>> IMHO cron should at least stat files in /etc/cron.d with known syntax >>> errors every time and recheck their syntax if the mtime has changed, not >>> only if other (valid) files have changed, vanished or popped up. done. > Please also take care that the new mtime may be lower (earlier) than > the one cached. This has always been the case (the condition is: old_mtime != new_mtime) Regards, Christian
signature.asc
Description: OpenPGP digital signature
