I seem to be having trouble running a daily cron job. This seems to be the only job that has trouble - nothing else has the "BAD FILE MODE" comment.
I googled the problem and found a suggestion that BAD FILE MODE probably means permissions trouble - but when I checked, it all looks fine. I'm looking for suggestions on how to proceed.
Here is the error message from my cron log: [EMAIL PROTECTED] ~]# more /var/log/cron | grep squidGuard Apr 18 17:11:31 localhost crond[2125]: (*system*) BAD FILE MODE (/etc/cron.d/squidGuard) Apr 19 11:11:11 localhost crond[2288]: (*system*) BAD FILE MODE (/etc/cron.d/squidGuard) Apr 19 11:17:39 localhost crond[2371]: (*system*) BAD FILE MODE (/etc/cron.d/squidGuard) Apr 19 13:29:07 localhost crond[2190]: (*system*) BAD FILE MODE (/etc/cron.d/squidGuard) [EMAIL PROTECTED] ~]# ls -l /etc/cron.daily/ total 92 -rwxr-xr-x 1 root root 418 Nov 19 12:21 00-makewhatis.cron -rwxr-xr-x 1 root root 135 Aug 18 2004 00webalizer -rwxr-xr-x 1 root root 276 Sep 28 2004 0anacron -rw-r--r-- 1 root root 797 Oct 19 2004 certwatch -rwxr-xr-x 1 root root 180 Oct 19 2004 logrotate -rwxr-xr-x 1 root root 2133 Nov 23 07:29 prelink -rwxr-xr-x 1 root root 104 Nov 1 18:54 rpm -rwxr-xr-x 1 root root 82 Oct 20 2004 slocate.cron -rwxr-xr-x 1 root root 56 Apr 16 20:00 squidGuard -rwxr-xr-x 1 root root 286 Aug 13 2004 tmpwatch -rwxr-xr-x 1 root root 136 Feb 21 07:38 yum.cron [EMAIL PROTECTED] ~]# I am running LTSP 4.2.0 - FC3
Any suggestions as to where the problem lies?
I recently spotted this problem as well.
You can either update or run this command to fix it:
chmod a-x /etc/cron.d/squidGuard
-Eric
signature.asc
Description: OpenPGP digital signature