Package: stunnel4 Version: 3:4.29-1 Severity: normal Hello,
I have a system where stunnel4 is installed and configured to start at boot. This morning, this host was restarted unexpectedly, and stunnel4 did not start at boot time. I tracked the problem down to a stale pidfile. During the boot process, the old pidfile still existed. Apparently, when the stunnel4 init script started, another process was running with the pid named in that file. The init script hence decided that stunnel4 was already running, and did not start it. Please implement some check that the process named in the pidfile is actually a stunnel4 process. I don't know what would be appropriate in the context of Debian policy and/or the package itself, but something like this seems necessary to ensure that stunnel4 recovers well from a bad reboot like this. Thank you for your consideration. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages stunnel4 depends on: ii adduser 3.112+nmu2 add and remove users and groups ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libssl0.9.8 0.9.8o-4squeeze13 SSL shared libraries ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii netbase 4.45 Basic TCP/IP networking system ii openssl 0.9.8o-4squeeze13 Secure Socket Layer (SSL) binary a ii perl-modules 5.10.1-17squeeze3 Core Perl modules stunnel4 recommends no packages. Versions of packages stunnel4 suggests: pn logcheck-database <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
