Package: chrony Version: 1.23-4 Severity: normal The new init script for chrony kills random netstat processes. This introduces a small race condition for systems also running munin. Munin uses netstat to plot the number of network connections. Killing the netstat process results in holes in the graphs and possibly warning mails.
Imho it always is a bad bad idea to do something like killall foo where foo is a common utility in a script. At least one proper way to do this is using the timeout package or maybe using a construct like ( netstat & ( sleep 1; kill $! ) ) | ... # untested which at least is less racy to kill munin's processes. Although this bug technically affects other packages I only mark it as normal (instead of critical), because it is unlikely to happen and has little impact. Helmut -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23.14 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages chrony depends on: ii libc6 2.7-16 GNU C Library: Shared libraries ii libreadline5 5.2-3 GNU readline and history libraries ii ucf 3.0010 Update Configuration File: preserv chrony recommends no packages. chrony suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
