I've already tried that but there's a problem : this command runs a new squidguard and doesn't use the current squidguard. This method can only detect a syntax error in the conf file.
Le ven 20/02/2004 � 14:52, Michael Wray a �crit : > use the example of testing squidguard in the FAQ which basically uses an: > echo "url"|squidGurad -c /path/to/conf.file > > The url should be something that you know is blocked by squidGuard. Write a > wrapper script to test for it, and send the result back....you'll basically > be looking for the line at the end that says either redirect or that > squidGuard is in Emergency mode. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Mikael Mourcia > Sent: Friday, February 20, 2004 6:19 AM > To: [EMAIL PROTECTED] > Subject: Monitor Squidguard > > > Hi, > > I want to build a cluster in my network for high availibility purpose. > The problem is that I don't know how I can consider Squidguard as dead > service. > I use squid and squidguard. I see when squid dies with "mon" and > tcp.monitor -p 3128. > But if squidguard dies, it doesn't mean that squid dies too. > > To sum up : How can I see that squidguard is in emergency mode ? > Thanks for our help. > Mikael > >
