Package: cron Version: 3.0pl1-86 My /etc/cron.d directory contains several symlinks, along these lines:
/etc/cron.d/foobar -> foobar.cron The *.cron files are sometimes updated by rsync from another machine; when that happens, their owner is temporarily set to that of a non-root user. The owner does get reset to root by my code, but there's a race: it's possible for cron to notice the file change before the ownership is fixed. That causes cron to log a message like this: Apr 29 13:34:01 marmoset /usr/sbin/cron[25373]: (*system*foobar) WRONG FILE OWNER (/etc/cron.d/foobar) However, cron does not notice when the ownership of the file is corrected, causing the jobs in that file not to get executed. Manually touching /etc/cron.d after the ownership is corrected does seem to persuade cron to reload the file. -- Aaron Crane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
