severity 618317 wishlist thanks
On Mon, Mar 14, 2011 at 11:52:11AM +0100, Vincent den Boer wrote: > It appears that the files in /etc/cron.d have naming requirements. When a > file ends in .cron (or maybe this also depends on other factors) no error > appears in the /var/log/cron.log (enabled through etc/rsyslog.conf), yet > the file is ignored. Please read the manpage: __________________________________________________________________________ (...) to add a crontab file to /etc/cron.d. Such files should be named after the package that supplies them. Files must conform to the same naming convention as used by run- parts(8): they must consist solely of upper- and lower-case letters, digits, underscores, and hyphens. If the -l option is specified, then they must conform to the LSB namespace specification, exactly as in the --lsbsysinit option in run-parts. __________________________________________________________________________ I think that the documentation is complete. > Cron should at least log an error. Besides that, the naming restrictions for > /etc/cron.d/ files should either be documented or removed. Naming restrictions are documented, and they have been for a long time. I can agree that cron could at least log an error when it finds a file in /etc/cron.d/ that it will not process. But we would have to check how to implement it so as to avoid spamming the logs. It might need to be a user-defined option since it is common for packages to leave '.dpkg-old' leftovers in /etc/cron.d/ which admins do not remove and we don't want this to have, as a consequence, a log entry repeated N times and (maybe) filling up whatever partition /var/ is located in. Thus, I'm downgrading this to 'wishlist' Regards Javier
signature.asc
Description: Digital signature
