Package: nfdump
Version: 1.6.6-1
Followup-For: Bug #736531
Dear Maintainer,
nfcapd's auto-expire functionality is broken in wheezy. When auto-expire is
enabled it only runs for the first time and then the launcher process is dead.
Stopping nfcapd fails because the launcher cannot be stopped. When the -x
option is used the command is also executed only for the first time.
The problem seems to be that in expire.c in function ExpireDir another signal
handler is set up for the same signals the launcher uses. The following changes
from upstream version 1.6.11 prevent this:
---------------------%<---------------------
$ diff nfdump-1.6.6/bin/expire.c nfdump-1.6.11/bin/expire.c
372,373c372,373
< SetupSignalHandler();
< if ( runtime )
---
> if ( runtime ) {
> SetupSignalHandler();
374a375
> }
---------------------%<---------------------
-- System Information:
Debian Release: 7.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nfdump depends on:
ii libc6 2.13-38+deb7u1
ii librrd4 1.4.7-2
ii lsb-base 4.1+Debian8+deb7u1
ii zlib1g 1:1.2.7.dfsg-13
nfdump recommends no packages.
nfdump suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
