Topic: SquidGuard

[Greg Zartman]

> Is it required to reboot the server to have Squidguard running?
> I need to install it in a production server, and would like
> to avoid
> rebooting.

No.  You can restart squid and apache using the run level scripts and squidguard will be up and running.

Greg Zartman

[Alejandro Lengua]

Thanks Greg,
but what do you mean by ""run level scripts"" ?

[Greg Zartman]

Alejandro Lengua wrote:
>
> Thanks Greg,
> but what do you mean by ""run level scripts"" ?

Scripts that manage services.  Run the following from a shell session.

Squid:  
/etc/rc.d/init.d/squid restart

Apache:
/etc/rc.d/init.d/httpd restart

Either that or you could reboot in the middle of the night...  Your people don't work around the clock do they?

Greg Zartman

[Alejandro Lengua]

Ah... that's easy...
Yes they work around the clock.. but I can have access to the hardware only at work hours.

[Tom Carroll]

Steve, I get somewhat the same error e-mail every day.  I double checked that the downloaded file is correct and sure enough it is.  I saw Cyrus Bharda's post, but do not know if squidguard is actually updating the blacklist.

Have you had any luck tracking this down?

I am running SME 5.6UDR-U4.  Here's what I receive each day for the error e-mail:
----
/etc/cron.daily/supdate.cron:

04:05:21 URL: ftp://ftp.teledanmark.no/pub/www/proxy/squidGuard/contrib/blacklists.tar.gz [430127] -> "blacklists.tar.gz" [1] tar (child): blacklists: Cannot read: Is a directory tar (child): At beginning of tape, quitting now tar (child): Error is not recoverable: exiting now

gzip: stdin: unexpected end of file
tar: Child returned status 2
tar: blacklists.tar.gz: Not found in archive
tar: Error exit delayed from previous errors
---
I searched the forums and this appears to be the only thread that mentions this problem specifically.

Tom