-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Nesbit wrote: [snip] > a) this is a known issue in older releases (can I be reasonably > assured that upgrading will prevent this from happening again?)
Yes, no. > b) until I understand the various components involved and test > upgrades on a staging system, is there anything I can do to mitigate > the chances of this failure happening again? Look at the contrib directory in the source distribution (i.e. clamavmon, clamdmon, clamdwatch). If "supervised by daemontools" didn't work use one of those. > c) can I expect an upgrade to be any more complex than > - removing clamav-libs (/usr/lib/libclamav.so.1 from install of > clamav-0.88-1.0.rh7.rf conflicts with file from package > clamav-libs-0.65-6) > - install/upgrade clamav-db and clamav The configuration file name changed to /etc/clamd.conf and you have to edit that one as well as /etc/freshclam.conf . HTH - -- René Berber -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iEYEARECAAYFAkPMBPcACgkQL3NNweKTRgwYcQCg6a7TKPSNmwS8cRa80MXoKuGT ZGoAoNlLNLgMEIvLLExrnRqUInyLpjjo =TY73 -----END PGP SIGNATURE----- _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
