Dale Walsh wrote: [snip]
I can't understand why everyone runs this through cron when it doesn't eat much memory or cpu cycles when run as a daemon?
If freshclam fails as a daemon you would not know it. If it fails as a cron job, then cron will let you know something is wrong.
Of course freshclam doesn't fail so this is only useful for user errors (like a bad path or permisions, etc.)
Besides, setting it up as a daemon needs more work, I would add it to the init.d/clamd script but that's my choice and is not there to make it easy. Yes, sometimes I'm lazy, adding it to cron takes 10 sec, adding it to the script probably takes 30 sec.
Just my opinion. -- René Berber
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
