So if we are using only clamscan from a cronjob and freshclamd to update the VSD then no need to startup clamd correct?
On Oct 12, 2016 5:35 AM, "Ralf Hildebrandt" <ralf.hildebra...@charite.de> wrote: > * Brad Scalio <sca...@gmail.com>: > > 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. > > > does it provide any added features or functionality not already present > > with freshclam + clamscan running on-demand from cronjobs? > > -- > Ralf Hildebrandt Charite Universitätsmedizin Berlin > ralf.hildebra...@charite.de Campus Benjamin Franklin > http://www.charite.de Hindenburgdamm 30, 12203 Berlin > Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 > _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
