From 7b20b3b4a8e42e21bc6830ec08d89b97951266a9 Mon Sep 17 00:00:00 2001
From: Matthias Andree <matthias.andree@gmx.de>
Date: Wed, 3 May 2006 00:07:42 +0000
Subject: Revise debug options to --nosyslog --nodetach -vvv.

svn path=/branches/BRANCH_6-3/; revision=4812
---
 fetchmail-FAQ.html | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

(limited to 'fetchmail-FAQ.html')

diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 2786fecd..47ed1acb 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -396,18 +396,17 @@ mail mangling</a>. There are lots of ways for other programs in the
 mail chain to screw up that look like fetchmail's fault, but you
 may be able to fix these by tweaking your configuration.</p>
 
-<p>A transcript of the failed session with -v -v (yes, that's
-<em>two</em> -v options, enabling debug mode) will almost always be
-useful. It is very important that the transcript include your
-POP/IMAP server's greeting line, so I can identify it in case of
-server problems. This transcript will not reveal your passwords,
-which are specially masked out precisely so transcripts can be
-passed around.</p>
+<p>A transcript of the failed session with "--nosyslog --nodetach -vvv"
+(yes, that's <em>three</em> -v options, enabling debug mode) will almost
+always be useful. It is very important that the transcript include your
+POP/IMAP server's greeting line, so I can identify it in case of server
+problems. This transcript will not reveal your passwords, which are
+specially masked out precisely so transcripts can be passed around.</p>
 
 <p>If you upgraded your fetchmail and something broke, you should
-include session transcripts with -v -v of both the working and
-failing versions. Very often, the source of the problem can
-instantly identified by looking at the differences in protocol
+include session transcripts with "--nosyslog --nodetach -vvv" of both
+the working and failing versions. Very often, the source of the problem
+can instantly identified by looking at the differences in protocol
 transactions.</p>
 
 <p>If the bug involves a core dump or hang, a gdb stack trace is
-- 
cgit v1.2.3