Dennis Peterson wrote: > Per Jessen wrote: >> Jay Lee wrote: >> >>> The point of the exercise it to run freshclam *only* when the update >>> is published, not to run every x hours (or minutes) without knowing >>> if there is an update. >>> >>> Looking at my options there... >> >> Why not just run freshclam as a daemon? > > Then you really need to have a daemon watcher to keep it going.
At some point you've got to trust someone/something. Who watches your daemon watcher? Who watches your OS? Who watches your power-supply? Quis custodiet ipsos custodes? ... > And it is actually used just a few seconds a day but as a daemon the > resources it uses are fully committed 100% of the day. Given the very limited amount of resources it uses, I see no problem in that. > At some point you just have to step back and take a simple approach, > especially when it's a simple problem. Running freshclam IS a simple option, IMHO. Anything else is needs additional scripting, checks of this and that etc. - not a simple approach at all. /Per Jessen, Zürich _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
