tag 627859 + confirmed thanks Hi Axel,
thanks for your detailed bug report! On 05/25/2011 12:40 AM, Axel Beckert wrote: > It seems to be a more seldom and not yet fixed special case of the > otherwise fixed http://bugs.debian.org/555954. As parts of #555954 > definitely have been fixed, I decided not to reopen #555954 but file a > new bug report and just refer to #555954. That, and #625495, a fix for which is currently pending. For the curious, [0] provides a detailed explanation of what is causing this. I initially considered merging this report with #625495, but then realized that the pending fix only recovers from filesystem errors (mode etc), not from syntax errors (missing newline). [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625495#10 > 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. > * Create a new in /etc/cron.d/, e.g. test3 > * Delete a file from /etc/cron.d/, e.g. test2 > * Restart cron. > 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. This is a great idea. I couldn't do that for the mode errors recovery because they don't change mtime, but fixing a syntax error would. I'll extend the recovery fix to do that. > So to be sure that I run the test without the danger of collateral > changes, I fully automated it. See script, syslog and output below. I haven't run it yet, but will use it to verify the fix. Thanks! Christian
signature.asc
Description: OpenPGP digital signature
