public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Harrison <eharrison@mail.mesd.k12.or.us>
To: dbentson@lcsd.k12.wa.us
Cc: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: Cron Problem for squidGuard - LTSP 4.0.2 (FC3)
Date: Thu, 21 Apr 2005 09:24:22 -0700	[thread overview]
Message-ID: <4267D3B6.2020303@mail.mesd.k12.or.us> (raw)
In-Reply-To: <4267CF2D.20305@lcsd.k12.wa.us>

[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]

Dan Bentson-Royal wrote:
> 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:
>      [root@localhost ~]# 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)
>      [root@localhost ~]# 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
>      [root@localhost ~]#
> 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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

  reply	other threads:[~2005-04-21 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 16:05 Cron Problem for squidGuard - LTSP 4.0.2 (FC3) Dan Bentson-Royal
2005-04-21 16:24 ` Eric Harrison [this message]
     [not found] ` <4a618d0805042109167b3627b6@mail.gmail.com>
2005-04-21 16:40   ` Dan Bentson-Royal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4267D3B6.2020303@mail.mesd.k12.or.us \
    --to=eharrison@mail.mesd.k12.or.us \
    --cc=dbentson@lcsd.k12.wa.us \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox