If you need anything, please let me know - This bug kinda haunts me a
little bit, and I'd really like to have it fixed.
Thanks
/Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: pmacct
Version: 0.12.5-4
In the current initscripts, the stop function has been changed to use
SIGTERM instead of SIGINT.
SIGTERM kicks the processes over in a way, that may cause sampled data
not yet pushed to backend storage to be lost. For this reason, please
change them back to
Perhaps something like this could be used instead? This has not been
thoroughly tested, so consider it a blueprint :-)
Idea: Initially, signal only the parent process with the INT signal to
let it gracefully end all its child-processes and itself. If the parent
process does not terminate within
Package: pmacct
Version: 0.12.5-1
Even though the pmacct packages provides the sfacctd, nfacctd daemons in
addition
to the pmacctd daemon, they are missing corresponding initscripts, default-files
and sample configs.
I've attached proposed files for inclusion - the sfacct ones, I've tested, the
Package: pmacct
Version: 0.12.5-1
At least, sfacctd (mysql plugin) seems to have problems correctly
reporting the bytes-count in flows. This results in one-hour byte-counts
in excess of 100TB on relatively inactive 4mbit links).
I've rebuild using the configure-flags: --enable-64bit
In the proposed initscripts, I've changed the stop function to use
SIGTERM instead of SIGINT. The reason for this is, that I was having
some database problems, that left the sfacctd processes running
(working), even after sfacct was sent a signal to stop. This could cause
old processes to still
6 matches
Mail list logo
