According to /usr/share/doc/vixie-cron-4.1-r10/FEATURES.bz2: -- If it exists, the /etc/cron.d/ directory is parsed like the cron spool directory, except that the files in it are not user-specific and are therefore read with /etc/crontab syntax (the user is specified explicitly in the 6th column). Vixie cron complains with this message in syslog: Jan 2 12:40:01 helot cron[12522]: (*system*) BAD FILE MODE (/etc/cron.d/update_google_safebrowsing.sh) but note it has nothing to do with file permissions. Reproducible: Always Steps to Reproduce:
Created attachment 139842 [details] Cron file to schedule updates
Created attachment 139843 [details, diff] ebuild patch Moves /etc/cron.d/update_google_safebrowsing.sh to /usr/sbin/ and installs a crontab spool file to /etc/cron.d/update_google_safebrowsing
incvs.