cron.daily reporting a squidGuard config problem
 

Hello,

I finally got Postfix configured to forward email from my Mandrake 10 Linux firewall to an email address I actually read, and now I get a daily email (below) from cron talking about a misconfiguration with squidGuard:

Subject: Cron <root@linuxbox> nice -n 19 run-parts /etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=test@example.com>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>
Message-Id: <20040907081838.611D99DBD@linuxbox.mydomain.org>
Date: Tue, 7 Sep 2004 04:18:38 -0400 (EDT)
X-pstn-levels: (S: 5.78364/99.14390 P:95.9108 )
X-pstn-settings: 3 (1.0000:1.0000) s gt3 gt2 gt1 p
X-pstn-addresses: from <test@example.com> forward (org good) [73/4]

error: squidGuard:17 unknown option 'A' -- ignoring line


Does anyone know how to fix this? I have looked at /etc/squid/squid.conf and didn't see anything. I searched the entire filesystem for a squidGuard.conf and found only the sample in /etc/squid (I am not running either squid or squidGuard).

Thanks in advance!

hmm, if you really are not using squid and squidguard, then open the MCC (mandrake control center), system, services, and turn off the service you don't need.

I'm not sure which version of the Drake you are using, so I'm assuming it is 10.something.

Sometimes these things get installed and turned on during installation, and you don't even realize they are happily or grumpily running in the background. :) wasting your cpu cycles from more important things, like Tux Racer!

Thanks for your reply. It is Mandrake 10. I had already stopped squid in the Services panel some time ago (it was interfering with logging into sites with integrated Windows authentication). I never configured or used squidGuard, and it does not appear in the Services panel to stop.

I'd be happy to correct whatever configuration setting the cron job is complaining about, but I have no idea what it could be. Any thoughts?

Thanks again.

Finally found this--the output was coming from cron's run of logrotate. In /etc/logrotate.d/squidGuard was the following text:

/var/log/squidGuard/advertising.log {
weekly
rotate 5
copytruncate
compress
notifempty
missingok
A
}

Not sure how the 'A' got in there, but it was the cause of the error.