I run a small network with a squid proxy, router and clients. All is well as long as allowed addresses are requested. But when a dis-allowed one is requested squidGuard shall redirect to another website. What happens is that lots of kdeinit processes are started until the machine freezes. Usually it reports that there is a timeout and that it cannot access the proxy. When I look at the squid access log I see the following (as many instances as there are processes in the client) e.g.:
1100508619.507 121321 192.168.x.x TCP_CLIENT_REFRESH_MISS/503 1414 GET <IP-address of dis-allowed site> - NONE/ - text/html

192.168.x.x is the address of the router on the proxy side.

What I should get is this:
1100508619.507 121321 192.168.x.x TCP_DENIED/503 1414 GET <IP-address of redirect site> - NONE/ - text/html

Where have I gone wrong?

just an idea:
if u have firewall, try to allow loopback
iptables -I INPUT -i lo -j ACCEPT

not to get off subject but how do you like squidguard? I also run squid, but thinking on adding squidguard to keep down the no no webpages

Unless something connected with iptables must be reloaded it doesn't help. And it looked to me as if it was allowed already????

The squid cache log gives umpteen messages as well, as follows:
2004/11/16 16:46:17 | comm_udp_sendto: FD 7, 213.142.64.170, port 53: (101) Network is unreachable
2004/11/16 16:46:17 | idnsSendQuery: FD 7: sendto: (101) Network is unreachable

As far as the usability of squidGuard goes I don't know yet. But it looks promising.

Hah! It works, the problem seems to be a timout connected with a very slow response from the redirect page. (The proxy is an old machine, so I didn't want to set up apache on it.)