Package: rdiff-backup Version: 1.2.8-7 Severity: normal Dear Maintainer,
After an automated backup process failed due to the remote host closing the connection, subsequent backup processes failed as well because rdiff-backup still checked, or tried to check, whether a process with the process id of the failed backup was running. I think that rdiff-backup should clear its pidfile whenever it stops due loss of connection with the remote host, or other fatal problems. Kind regards, Arnold Metselaar -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (650, 'stable'), (550, 'oldstable'), (500, 'stable-updates'), (500, 'oldstable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rdiff-backup depends on: ii libc6 2.19-18+deb8u6 ii librsync1 0.9.7-10 ii python 2.7.9-1 ii python2.7 2.7.9-2+deb8u1 Versions of packages rdiff-backup recommends: ii python-pylibacl 0.5.2-1 ii python-pyxattr 0.5.3-1 rdiff-backup suggests no packages. -- no debconf information
