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). 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 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. 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? Bye, -- Loïc Minier <[EMAIL PROTECTED]> "You can gtk_main_run, but you can't gtk_widget_hide." --danw, 19-jul-04
