This one time, at band camp, Loïc Minier said: > Hi, > > On Sun, May 07, 2006, Stephen Gran wrote: > > Doing it at run time relies on having a hard coded path to the clamd > > binary embedded in freshclam, and this feels wrong to me. > > Yes, hence the "ugly" (well, there's no reason you couldn't reuse the > PATH from configure in freshclam).
My problem with this is that it actually loses flexibility over the current method. freshclam does have path prefix and path to clamd.conf available to it, but right now, you can specify an alternate clamd.conf as an option to NotifyClamd (e.g., NotifyClamd /usr/local/etc/clamd.conf) Specifying a single binary check loses the ability to have freshclam notify an out of band clamd in this way. > I can imagine how it would be easier to e.g. create a freshclam > configuration derived from freshclam.conf before running the crontab > and disabling Notify if clamd isn't installed. I am not sure I understand you here. At any rate, freshclam does not support reading an alternate config file. > > I am saying that your configuration choices have created this > > situation. The fact that you have freshclam running from cron > > rather than as a daemon means that you did not take the defaults. > > The defaults set freshclam up as a daemon process, and it only > > outputs to it's logfile. There are no spurious emails to root for > > this in the default configuration. All I am saying is, if you can > > handle changing one debconf option, surely you can handle changing a > > second? > > Now that you mention it, I recall selecting to run freshclam from > cron instead of running as a daemon indeed. > > This renders the bug less frequent, and its severity less important > of course. > > I see both clamav-freshclam/autoupdate_freshclam and > clamav-freshclam/NotifyClamd are priority medium questions, so I can > only assume I incorrectly selected a stupid configuration where clamd > should be notified of upgrades even when clamd isn't installed. > > However, it also seems to me as this error is always triggered, but > only visible when I select cron because cron creates a mail when an > error occurs. Yes. Since the condition is itself harmless in the default arrangement, though, I am not sure it's really an issue. Upstream has NotifyClamd defaulted to off, and I suppose I could change to that, but I purposely arranged the packages so that the normal install of clamd will mostly work, and freshclam will notify it on updates, which is what most people want. The packaging does try to be all things to all people, but I can't simultaneously satisfy conflicting desires. > If this is correct, I still consider it a nice robustness feature to > avoid trying a clamd notification when it's not installed, but with a > very low priority. > > What do you think? It seems reasonable on the face of it, but again, I don't immediately see a way to know which clamd to check for. If you can think of that, I will implement it. Take care, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
