Package: samhain Version: 2.2.3-6.2 Severity: normal Hello,
I see that samhain does not write a pidfile of it's own, and so you are using --exec in the stop target. This doesn't work - when there's a security upgrade or anything else that will change the on disk executable from what is running, the stop target will fail. It's usually sufficient (the daemon will usually be stopped in prerm before the new binary is unpacked), but it's needlessly fragile. It would be better to use start-stop-daemon's ability to write a pidfile for the daemon, or (better) patch samhain to write a pidfile itself. Cheers, -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.29.4-dsa-dl380-oldxeon (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/bash Versions of packages samhain depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-18 GNU C Library: Shared libraries ii libgcrypt11 1.4.1-1 LGPL Crypto library - runtime libr ii libgnutls26 2.4.2-6+lenny1 the GNU TLS library - runtime libr ii libprelude2 0.9.18.1-1 Hybrid Intrusion Detection System samhain recommends no packages. samhain suggests no packages. -- debconf information: samhain/init-log: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
