The ebuild create /etc/cron.daily/logrotate.cron but the dot is a forbidden character for a cron filename. So crond ignore this filename and no logrotate is done. Reproducible: Always Steps to Reproduce: 1. emerge logrotate 2. 3. Actual Results: The logrotate cron file is installed as /etc/cron.daily/logrotate.cron Expected Results: The logrotate cron file is installed as /etc/cron.daily/logrotate
Which crond do you use?
vixie-cron But anyway, this is not relevant, some other crond could ignore this file. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609162
It does matter which cron you use, because sys-process/dcron doesn't have this problem, for one thing.
I have two boxes with =sys-process/vixie-cron-4.1-r12 installed and it works fine, all files under /etc/cron.* are executed, even those with dots in their filenames (including logrotate.conf) Tested with fcron and works ok too. By looking at script /usr/sbin/run-crons (from the =sys-process/cronbase-0.3.3): http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/cronbase/files/run-crons-0.3.3?revision=1.1&view=markup you can check that all scripts under /etc/cron.{hourly,daily,weekly,monthly} are executed no matter their names contain a dot or not: for SCRIPT in $CRONDIR/* ; do ... Can you take a look at your /etc/crontab to see if /usr/sbin/run-crons is executed properly?. That is, contains a line like: */10 * * * * root test -x /usr/sbin/run-crons && /usr/sbin/run-crons Thanks for reporting.
My initial problem is resolved, all files under /etc/crond.daily hasn't exec perms. So my logrotate reworks now. But I think adding .cron is still a bad idea.
How was this bug resolved. Why would it suddenly be invalid?
Package removed.
