Yes got it, many thanks for the replies -- gotta admit it's always a pleasure to post questions here as I know I will get a response, and sometimes some well deserved sarcasm.
On Wed, Oct 12, 2016 at 8:14 AM, Reindl Harald <[email protected]> wrote: > > > Am 12.10.2016 um 12:15 schrieb Brad Scalio: > >> So if we are using only clamscan from a cronjob and freshclamd to update >> the VSD then no need to startup clamd correct? >> > > it's easy: if you don't use it you don't need it to start > if you use clamscan and nothing else you don't use it > > On Oct 12, 2016 5:35 AM, "Ralf Hildebrandt" <[email protected]> >> wrote: >> >> * Brad Scalio <[email protected]>: >>> >>>> When a clamscan is ran from cmdline or via cron is the virus signature >>>> database checked before scanning commences >>>> >>> >>> It is loaded, thus the long startup time. >>> >>> in a fashion that if we aren't using clamdscan then is there a need for >>>> clamd to run, >>>> >>> >>> No. clamdscan together with clamd eliminated the long startup time >>> >> _______________________________________________ > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml > _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
