Package: libclamav1 Version: 0.88-4 Severity: wishlist Since both clamd and freshclam are dynamically linked against libclamav, shouldn't they be restarted when libclamav is upgraded? Doesn't seem to happen currently:
Unpacking replacement libclamav1 ... Setting up libclamav1 (0.88-4) ... diz $ date Wed Feb 15 13:18:20 GMT 2006 diz $ ps -ef | grep clam clamav 5177 1 0 Feb13 ? 00:00:04 /usr/sbin/clamd clamav 5232 1 0 Feb13 ? 00:00:00 /usr/bin/freshclam -p /var/run/clamav/freshclam.pid -d --quiet cheers, calum. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages libclamav1 depends on: ii libbz2-1.0 1.0.3-2 high-quality block-sorting file co ii libc6 2.3.6-1 GNU C Library: Shared libraries an ii libcomerr2 1.38+1.39-WIP-2005.12.31-1 common error description library ii libcurl3 7.15.1-1 Multi-protocol file transfer libra ii libgmp3c2 4.1.4-11 Multiprecision arithmetic library ii libidn11 0.5.18-1 GNU libidn library, implementation ii libkrb53 1.4.3-5 MIT Kerberos runtime libraries ii libssl0.9.8 0.9.8a-7 SSL shared libraries ii zlib1g 1:1.2.3-9 compression library - runtime libclamav1 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
