From 3a27df341c39eaf7b2181d3f036c68b080e07a74 Mon Sep 17 00:00:00 2001 From: Matthias Andree Date: Mon, 31 Jul 2006 23:27:50 +0000 Subject: Fix SIGHUP behavior, broken since 5.9.13 (r3692). svn path=/branches/BRANCH_6-3/; revision=4871 --- NEWS | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'NEWS') diff --git a/NEWS b/NEWS index fc00b061..ff107336 100644 --- a/NEWS +++ b/NEWS @@ -32,6 +32,8 @@ change. MA = Matthias Andree, ESR = Eric S. Raymond, RF = Rob Funk.) * The "protocol auto" default inside fetchmail may be removed from a future fetchmail release. Explicit configuration of the protocol is recommended. * Kerberos IV support may be removed from a future fetchmail release. +* SIGHUP wakeup may be removed from a future fetchmail release and cause it + to terminate. -------------------------------------------------------------------------------- @@ -89,6 +91,11 @@ fetchmail 6.3.5 (not yet released): * Avoid compiling empty files, to avoid diagnostics from strict compilers. * If the lockfile ends before the process ID, treat it as stale and unlink it. Reported by Justin Pryzby, Debian Bug #376603. +* SIGHUP wake-up behavior was broken since 5.9.13's Cygwin changes, in that for + non-root users, SIGHUP would abort the first poll and subsequently interfere + with new polls, and SIGHUP would be ignored for root users. SIGHUP now matches + documented behavior. SIGUSR1 has always been a wakeup signal for both root + (undocumented) and non-root users. See also the deprecation warning above. # CHANGES: * Rename all fetchmail-internal lock_* functions to fm_lock_*. Obsoletes -- cgit v1.2.3