Hello,
> ls -d bin/* | parallel clamscan
> looks easy but logging may be difficult in this case too.
ls -d bin/* |parallel clamscan --no-sumary {} >yourlogfile.txt works fine.
Anyway, this is time consuming and require a huge RAM. Because on a 8 thread
CPU, 8 instance of clamscan will be run. S
Exactly.
dp
On 6/23/15 10:24 AM, MarkusGMX wrote:
Am 23/06/15 um 14:10 schrieb Gene Heskett:
On Monday 22 June 2015 19:01:34 Dennis Peterson wrote:
And be careful if using the -l option of clamscan.
And what might that result in?
Warnings like that demand a scenario describing statement wh
On Tuesday 23 June 2015 13:24:11 MarkusGMX wrote:
> Am 23/06/15 um 14:10 schrieb Gene Heskett:
> > On Monday 22 June 2015 19:01:34 Dennis Peterson wrote:
> >> And be careful if using the -l option of clamscan.
> >
> > And what might that result in?
> >
> > Warnings like that demand a scenario descr
Am 23/06/15 um 14:10 schrieb Gene Heskett:
On Monday 22 June 2015 19:01:34 Dennis Peterson wrote:
And be careful if using the -l option of clamscan.
And what might that result in?
Warnings like that demand a scenario describing statement where it could
backfire.
Perhaps he is thinking of th
On Monday 22 June 2015 19:01:34 Dennis Peterson wrote:
> And be careful if using the -l option of clamscan.
And what might that result in?
Warnings like that demand a scenario describing statement where it could
backfire.
> On 6/22/15 1:13 PM, Noel Jones wrote:
> > On 6/22/2015 2:50 PM, MarkusG
