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
wrote:
>
>
> Am 12.10.2016 um 12:15 schrieb Brad Scalio:
>
>> So if we
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
On 12.10.16 06:15, Brad Scalio wrote:
So if we are using only clamscan from a cronjob and freshclamd to update
the VSD then no need to startup clamd correct?
correct, but don't blame clamscan long signature loading time (and thus for
long run time)
On Oct 12, 2016 5:35 AM, "Ralf Hildebrandt"
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"
wrote:
> * Brad Scalio :
> > When a clamscan is ran from cmdline or via cron is the virus signature
> > database checked before scan
* Brad Scalio :
> 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 c
When a clamscan is ran from cmdline or via cron is the virus signature
database checked before scanning commences in a fashion that if we aren't
using clamdscan then is there a need for clamd to run, does it provide any
added features or functionality not already present with freshclam +
clamscan r
