From 460c55279cbe55ba56f7068ace6e7cadbb6d6df1 Mon Sep 17 00:00:00 2001 From: Matthias Andree Date: Tue, 13 Oct 2020 17:21:47 +0200 Subject: pidfile/lockfile handling bugfixes pidfile/locking: log errors thru syslog, too This works by replacing perror()/fprintf(stderr, ...) by report() and strerror(). If the pidfile cannot be unlinked, truncate it. Bump release version to 6.4.13.rc1, and move KNOWN BUGS section up in NEWS. --- NEWS | 26 ++++++++++++++++++++++---- 1 file changed, 22 insertions(+), 4 deletions(-) (limited to 'NEWS') diff --git a/NEWS b/NEWS index 7b9db2e7..727010c1 100644 --- a/NEWS +++ b/NEWS @@ -64,12 +64,22 @@ removed from a 6.5.0 or newer release.) for end-of-life OpenSSL versions may be removed even from patchlevel releases. --------------------------------------------------------------------------------- -fetchmail-6.4.12 (released 2020-09-04, 27596 LoC): +fetchmail-6.4.13 (work in progress): # BUG FIXES: -* The README file is now the one from Git again. The makerelease.pl script - used to roll and upload the tarball sometimes clobbered the README file and - replaced its contents by a part of the NEWS file. +* Errors about lock file (= pidfile) creation could be lost in daemon + configurations (-d option, or set daemon) when using syslog. Now they are also + logged to syslog. Found verifying a pidfile creation issue on 6.4.12 that was + previously reported by Alex Hall of Automatic Distributors. +* If the lock file cannot be removed (no write permission on directory), try + to truncate it, and if that fails, report error. +* If the pidfile was non-default, fetchmail -q or --quit would malfunction and + claim no other fetchmail were running, because it did not read the + configuration files or merge the command line options, thus it would look for + the PID in the wrong file. + +# CHANGES: +* Lockfile (= pidfile) creation errors are now logged with filename and reason. # KNOWN BUGS AND WORKAROUNDS (This section floats upwards through the NEWS file so it stays with the @@ -91,6 +101,14 @@ fetchmail-6.4.12 (released 2020-09-04, 27596 LoC): messages. This will not be fixed, because the maintainer has no Kerberos 5 server to test against. Use GSSAPI. +--------------------------------------------------------------------------------- +fetchmail-6.4.12 (released 2020-09-04, 27596 LoC): + +# BUG FIXES: +* The README file is now the one from Git again. The makerelease.pl script + used to roll and upload the tarball sometimes clobbered the README file and + replaced its contents by a part of the NEWS file. + --------------------------------------------------------------------------------- fetchmail-6.4.11 (released 2020-08-28, 27596 LoC): -- cgit v1.2.3