Package: squid Version: 2.5.9-10sarge2 Squid does a blocking write to the syslog socket from the main proccess. If this write blocks, the proxy comes to a grinding halt until the syslog completes. Worse still, squid logs some information via syslog despite all of the *_log directives requesting logging directly to files.
Squid should log exclusively to the destinations configured with the *_log configuration directives. If one of those destinations requires syslog, squid must use non-blocking IO. If a non-blocking syslog implementation isn't available, squid should launch one or more helper processes to use the blocking interface. -- Brian Ristuccia [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
