I alredy tried it. The return code is always 0. I will try the second option. Em Qui 20 Jan 2005 16:59, Chris Francy escreveu: > Humm I know if you start the squidGuard process manually with a invalid > config file it seems to set the exit status too 1. > > So this below script find tell you if their was an error. Of course if the > config file is good then squidGuard will start running and never get to the > error test. > > #!/bin/bash > squidGuard -c configfile -d > if [ $errst -eq 1 ]; then > echo "squidguard failed-bad config" > exit 1 > fi > > > Perhaps you could write a script that started squidGuard as a seperate > process in the background, grabbed the PID. Then maybe make it watch the > log file for good/bad messages and kill when the answer was found. > > It may be easier to hack a config test into squidguard though. > > Chris > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Marcelo Araujo > Sent: Thursday, January 20, 2005 7:44 AM > To: [email protected] > Subject: squidguard status > > > Hi list > > We are using squidguard with squid and we need to make some way to parse > squidguard config file before reload squid and return a errorlevel or a > simple message. > > We have how to do that? Thanks in advance.
-- Constat ::: Comprometimento Gerando Resultados Marcelo J. C. de Araujo Analista de Seguran�a Certifica��o LPI - Level 1 Conectiva Linux - Certifica��o Avan�ada Certifica��o Trend Validated Technician Certifica��o Trend Network VirusWall Level II Certifica��o Trend IMSS v5.5 Constat-POA http://www.constat.com.br 51 33306699 D�vidas, Sugest�es, Reclama��es ? mailto:[EMAIL PROTECTED]
