From a84f5650eeaae447745938c9c12d868b6c021a41 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sun, 14 Dec 2008 16:34:32 +0000 Subject: [PATCH] - Mention the new log level for crunched requests. - In the mingw32 entry, replace "mutex locks" with "critical sections". --- ChangeLog | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 44f4354f..f7c32e72 100644 --- a/ChangeLog +++ b/ChangeLog @@ -3,11 +3,16 @@ ChangeLog for Privoxy -------------------------------------------------------------------- *** Since 3.0.10 +- Crunched requests are logged with their own log level. + If you used "debug 1" in the past, you'll probably want + to additionally enable "debug 1024", otherwise only passed + requests will be logged. If you only care about crunched + requests, simply replace "debug 1" with "debug 1024". - A "clear log" view option was added to the mingw32 version to clear out all of the lines in the Privoxy log window. Based on a patch submitted by T Ford. -- The mingw32 version uses mutex locks now which prevents - log message corruption under load. As a side effect, +- The mingw32 version uses "critical sections" now which + prevents log message corruption under load. As a side effect, the "no thread-safe PRNG" warning could be removed as well. - Support for remote toggling is controlled by the configure option --disable-toggle only. In previous versions it also -- 2.39.2