From c37b5d80dcbc0b30427ac7671b9eccd8856b1579 Mon Sep 17 00:00:00 2001
From: Matthias Andree <matthias.andree@gmx.de>
Date: Mon, 7 Aug 2006 08:38:52 +0000
Subject: Freeaddrinfo() fix for Uli Zappe's bug. This might fix Debian
 Bug#294547 and Bug#377135.

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

(limited to 'fetchmail-FAQ.html')

diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index dce7b38c..df7d3f8c 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -2487,15 +2487,9 @@ declaration <tt>auth password</tt> in your .fetchmailrc.</p>
 <h2><a id="R13" name="R13">R13. What does "Interrupted system call"
 	mean?</a></h2>
 
-<p>Fetchmail 6.3.5 and newer gave up on the older timeout handling which
-could cause unstable behavior. Instead, timeouts now interrupt
-long-running functions and are reported as "Interrupted system
-call".</p>
-
-<p>While this loses accuracy of timeout reporting, there is
-unfortunately no safe way for C to make extensive use of error
-reporting, and the amount of code that would need to be added is too
-large for a stable series as 6.3.X is.</p>
+<p>Non-fatal signals (such as timers set by fetchmail itself) can
+interrupt long-running functions and will then be reported as
+"Interrupted system call". These can sometimes be timeouts.</p>
 
 <hr/>
 <h1>Hangs and lockups</h1>
-- 
cgit v1.2.3