Your message dated Wed, 22 Feb 2006 09:48:27 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352956: libclamav1: postinstall should restart clamd and
freshclam
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
This one time, at band camp, Calum Mackay said:
> hi Stephen,
> >Imagine having to figure out all of the services running on a machine
> >that use a given library and restart them all. It is technically
> >possible of course, but it is non-trivial.
>
> I wonder: in theory, we ought to easily be able to find any installed
> pkgs that have a dependency on a given shared lib pkg, and then just
> call their restart methods. But is there a generic way to restart
> services provided by a pkg when you only know the name of the pkg?
For the most part, the init script has the same name as the package, but
not always. This is where it gets harder, and this is the part I meant.
We could do it this way:
look up all the packages that depend on the library
look up which of those are installed
check if any of them have init scripts
restart the ones that do
But as you can imagine, that would make upgrades sloooow. Imagine a
standard testing or unstable upgrade - it might involve doing this
seventy times for various library packages.
It might at some point make sense to have a generic hook in dpkg that
remembers what libraries have been upgraded in single run, and then at
the end do the calculation once and restart the whole lot at once.
Feel free to submit a wishlist bug against dpkg for that - it's not a
bad idea.
> >In this particulare case, I also feel it's mostly a no-op, since the
> >packages for the daemons are also upgraded at the same time, in the most
> >common case, so it should take care of itself.
>
> right, although for some reason not in this case? That might just have
> been a side-effect of a failed download, or something.
>
> no problem, feel free to close... :)
OK, will do. Thanks,
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : [EMAIL PROTECTED] |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------
signature.asc
Description: Digital signature
--- End Message ---
