I recently had a problem with squidGuard 1.2.0 suddenly going into emergency mode with the following error:
2002-03-02 13:46:08 [11526] overflow in vsprintf (sgLogError): Success 2002-03-02 13:46:08 [11526] going into emergency mode After this happened, most requests were going through unfiltered, although occasionally it would work. A 'squid -k reconfigure' fixed it, and it hasn't happened since. I took a look in the list archives and found only one mention of this happening before. However, it was with squidGuard 1.1.4 (I'm running 1.2.0). The response said it had to do with the buffersize of log entries, and that this would be fixed in the next version of squidGuard. So I guess my question is: was this really fixed in 1.2.0, and if so, what could still be causing this to happen? Thanks! -- Craig Xpressweb Internet Services [EMAIL PROTECTED] http://www.xpressweb.com
