Summary: | ClamAV 0.70 ebuild should restart clamd | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Remco Barendse <remco> |
Component: | New packages | Assignee: | Antivirus Team <antivirus> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Remco Barendse
2004-05-11 10:29:30 UTC
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) |