Sounds like you're not making the database files off-line, rather you're
making them as squid starts. It shouldn't take that long with a 1.4 GHz
machine (mine was a C500 for ages)
Try this command as root
squidGuard -C all
to generate the .db files from the text files
Then give a
squid -k reconfigure
to make squid notice the new databases.
On Sun, 2003-03-02 at 03:42, Amy Anderson wrote:
> I will certinly try that, I am running a 1.4mhz with 2 120gb hard drive
> and 2 512mb chips of ram,
How much disk is allocated to squid for caching? have you given it 240
Gb or something huge? I have allocated 12 Gb, and that represents over
a month's volume cap for us.
> and when I have squid running our branch
> offices are not able to telnet in because it is so slow. I had several
> DNS fail on one website we use on a constant basis and it locks everyone
> out of it even though it has been used all day log. This page is a
> county applet driven database of documents that we can print (like for
> title searches when someone buys a home) Those are the only 2 reasons
> for eventhinking of turning off squid at the main branch. I have squid
> and squidguard running fine on the smaller servers with less traffic. I
> am going to try your idea and see if it helps. I appreciate your help
> very much.
>
> This is the page we are getting even
>
> The requested URL could not be retrieved
>
>
> While trying to retrieve the URL: %U
>
>
> The following error was encountered:
>
> Unable to determine IP address from host name for %H
>
> The dnsserver returned:
>
> %z
>
> This means that:
>
> The cache was not able to resolve the hostname presented in the URL.
> Check if the address is correct.
>
>
> Your cache administrator is %w.
>
