From: Fabian Keil Date: Sun, 15 Nov 2009 14:22:41 +0000 (+0000) Subject: Describe how to get a meaningful logfile. X-Git-Tag: v_3_0_16~120 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=dab351ef688135e9b275fc10fb4b9387daa964a2 Describe how to get a meaningful logfile. --- diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml index 2aa54700..647af1b4 100644 --- a/doc/source/contacting.sgml +++ b/doc/source/contacting.sgml @@ -3,7 +3,7 @@ Purpose : Entity included in other project documents. - $Id: contacting.sgml,v 2.13 2008/01/17 01:49:51 hal9 Exp $ + $Id: contacting.sgml,v 2.14 2008/04/26 11:38:51 fabiankeil Exp $ Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/ See LICENSE. @@ -214,7 +214,25 @@ Please be sure to provide the following information: Any other pertinent information to help identify the problem such as config or log file excerpts (yes, you should have log file entries for each - action taken). + action taken). To get a meaningful logfile, please make sure that the + logfile directive + is being used and the following debug options are enabled: + debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. +debug 2 # show each connection status +debug 4 # show I/O status +debug 8 # show header parsing +debug 128 # debug redirects +debug 256 # debug GIF de-animation +debug 512 # Common Log Format +debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why. +debug 4096 # Startup banner and warnings. +debug 8192 # Non-fatal errors + If you are having trouble with a filter, please additionally enable + debug 64 # debug regular expression filters + Note that Privoxy log files may contain sensitive information so please don't + submit any logfiles you didn't read first. You can mask sensitive information + as long as it's clear that you removed something.