[clamav-users] High freshclam process' CPU usage since last night PDT...

[PhiLLip Pi]

Ah, it is a known issue. Thanks, Al. I will wait. Yeah, this is an issue 
for slow machines like mine. :(


On 6/8/2017 3:19 PM, Al Varnell wrote:
> Phillip,
>
> Did you see this earlier today?
>
> On Thu, Jun 08, 2017 at 05:13 AM, Mark Allan wrote:
>> For some reason, applying the 4MB daily-23454.cdiff file took a really long time, even on a fast machine - 6 minutes on a 2.6 GHz intel core i7
>>
>> Curiously, the main-58.cdiff took only a fraction of that time (less than 30 seconds) to apply, despite being twice the size.
>>
>> So I'm wondering, when posting a new main.cvd in the future, is there a way to decrease the size of the daily cdiff files by having more of them, or would that not help with the processing time?  Is there any way to do it without making it look like freshclam has hung?
>>
>> Mark
>
>
> On Thu, Jun 08, 2017 at 03:02 PM, PhiLLip Pi wrote:
>>
>> Hello.
>>
>> My updated 64-bit Debian's stable/Jessie's top shows "4959 clamav    20  0  106684  22856  12836 R 100.0  1.1   0:58.70 freshclam".
>>
>> Its /var/log/clamav/freshclam.log's ending show:
>> Thu Jun  8 14:43:18 2017 -> --------------------------------------
>> Thu Jun  8 14:43:18 2017 -> freshclam daemon 0.99.2 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
>> Thu Jun  8 14:43:18 2017 -> ClamAV update process started at Thu Jun  8 14:43:18 2017
>> Thu Jun  8 14:43:19 2017 -> main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
>> Thu Jun  8 14:43:22 2017 -> Downloading daily-23454.cdiff [100%]
>>
>> I had to stop clamav-freshclam (via systemctl): clamav-freshclam.service to get my CPU back with "sudo /etc/init.d/clamav-freshclam stop" command. Log shows:
>> Thu Jun  8 14:45:02 2017 -> Update process terminated
>>
>> It had been like this since last night PDT. Is it just me or are others having this issue too?
>>
>> Thank you in advance. :)
>
> -Al-