I'm a little reluctant to fire up a daemon process just to scan a system once a month or once a quarter. As I said, we aren't looking for malware, so I don't really care if the database is somewhat out of date and we aren't scanning email, so I don't think the performance hit from multiple threads is really going to come into play.
I'm just looking for an easier way to manage the configuration fed to the on-demand scan (exclusion list and logging options primarily). Do I really need to stand up and maintain a daemon for that? fpsm On Sun, Sep 23, 2012 at 12:00 PM, Peter Bonivart <[email protected]> wrote: > On Sun, Sep 23, 2012 at 5:55 PM, Fredrich Maney <[email protected]> > wrote: >> Is there a better way to do this that I'm overlooking? > > Using clamDscan? > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml -- Fredrich Maney +1.502.509.2594 google [email protected] _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
