I have updated ClamAV from 0.67 to 0.70 and left clamd running. This way the freshclam process keeps running for the old version of clamav which keeps complaining in clam-update.log "WARNING: Your ClamAV installation is OUTDATED - please update immediately !" even though the box is running 0.70. Restarting clamd solved the problem, but viruses slipped through undetected?! Reproducible: Always Steps to Reproduce: 1.re-emerge clamav to upgrade 2.do not restart clamd 3.check for viruses undetected by your old clamav that should have been caught by the new version Actual Results: viruses slipped through Expected Results: the ebuild should have checked if clamd was running, stop it and re-start it after emerging
i don't think this is a clamav problem .. you probably want _Every_ pakage to restart it's services after re-emerging it right? (i don't know of any ebuild that does that . correct me if i'm wrong ;)) i'm not sure though whom to assign to.
Good question, I guess that for most packages indeed it would be desirable to have the package restarted after upgrading or re-emerging. For others it is not convenient at all. I I upgrade Samba on a production server I would have to see it restart during workhours when people are working on it and lose their connection with the server. That would be a quick way to have my phone ringing red hot :) But in this case for the virus scanner it is convenient and can probably be restarted without causing havoc on other processes. The ebuild should at least contain a warning that box will keep running the old version of clam and that the new version will only be used after restarting clamd.
added a warning in pkg_postinst for all clamav ebuilds (restarting it is maybe not the best idea but warning the users should be enough)