From d586877b16a6549a40ef5915442e1692d09871fb Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Fri, 7 Dec 2007 16:45:15 +0000 Subject: [PATCH] Enable logfile again, but only log fatal errors. --- doc/source/p-config.sgml | 75 ++++++++++++++++------------------------ 1 file changed, 29 insertions(+), 46 deletions(-) diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index 5abd272c..e4fe7fd9 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -3,7 +3,7 @@ Purpose : Used with other docs and files only. - $Id: p-config.sgml,v 2.22 2007/11/09 20:26:58 fabiankeil Exp $ + $Id: p-config.sgml,v 2.23 2007/11/15 02:47:01 hal9 Exp $ Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/ See LICENSE. @@ -95,7 +95,7 @@ Sample Configuration File for Privoxy v&p-version; - $Id: p-config.sgml,v 2.22 2007/11/09 20:26:58 fabiankeil Exp $ + $Id: p-config.sgml,v 2.23 2007/11/15 02:47:01 hal9 Exp $ Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/ @@ -835,13 +835,6 @@ actionsfile Notes: - The logfile is where all logging and error messages are written. The level of detail and number of messages are set with the debug @@ -851,15 +844,14 @@ actionsfile is doing. - Many users will never look at it, however, and it's a privacy risk - if third parties can get access to it. It is therefore disabled by - default in Privoxy 3.0.7 and later. + Depending on the debug options below, the logfile may be a privacy risk + if third parties can get access to it. As most users will never look + at it, Privoxy 3.0.7 and later only log fatal + errors by default. - For troubleshooting purposes, you will have to explicitly enable it. - Please don't file any support requests without trying to reproduce - the problem with logging enabled first. Once you read the log messages, - you may even be able to solve the problem on your own. + For most troubleshooting purposes, you will have to change that, + please refer to the debugging section for details. Your logfile will grow indefinitely, and you will probably want to @@ -867,19 +859,6 @@ actionsfile (see man cron). For Red Hat based Linux distributions, a logrotate script has been included. - Any log files must be writable by whatever user Privoxy is being run as (on Unix, default user id is privoxy). @@ -888,7 +867,7 @@ fk 2007-11-07 -@@#logfile logfile]]> +@@logfile logfile]]> @@ -1102,24 +1081,23 @@ fk 2007-11-07 A debug level of 1 is informative because it will show you each request - as it happens. 1, 4096 and 8192 are highly recommended - so that you will notice when things go wrong. The other levels are probably - only of interest if you are hunting down a specific problem. They can produce - a hell of an output (especially 16). + as it happens. 1, 4096 and 8192 are recommended + so that you will notice when things go wrong. The other levels are + probably only of interest if you are hunting down a specific problem. + They can produce a hell of an output (especially 16). - - If you want to use CLF (Common Log Format), you should set debug + If you want to use pure CLF (Common Log Format), you should set debug 512 ONLY and not enable anything else. @@ -1127,13 +1105,18 @@ fk 2007-11-07 length of log messages. If it's reached, messages are logged truncated and marked with ... [too long, truncated]. + + Please don't file any support requests without trying to reproduce + the problem with increased debug level first. Once you read the log + messages, you may even be able to solve the problem on your own. + -@@debug 1 # show each GET/POST/CONNECT request]]> -@@debug 4096 # Startup banner and warnings]]> -@@debug 8192 # Errors - *we highly recommended enabling this*]]> +@@#debug 1 # show each GET/POST/CONNECT request]]> +@@#debug 4096 # Startup banner and warnings]]> +@@#debug 8192 # Errors - *we highly recommended enabling this*]]> -- 2.39.2