[Pkg-clamav-devel] Bug#971842: Bug#971842: clamav-daemon erroneously reports "Failed with result 'timeout'" when stopped

[Dominik Reusser]

Dear Sebastian,

sorry for the late reply

most likely, the daemon is swapped out. We are talking about a memory
restricted system with the obligation to run daily scans on the file
system. It seems that running clamdscan with the daemon is still faster
while scanning the major part of the file system, compared to running
clamscan, even if the daemon uses some swap space.

Obviously, this setup is not optimal. I looked into running clamdscan
against a service on a different system in the same network, but this seems
not to be supported out of the box.

Would it hurt to increase the timeout or make it adjustable?

Dominik

Am Mi., 20. Jan. 2021 um 08:05 Uhr schrieb Dominik Reusser <
dr896543 at gmail.com>:

>
>
> Dear Sebastian,
>
> most likely, the daemon is swapped out. We are talking about a memory
> restricted system with the obligation to run daily scans on the file
> system. It seems that running clamdscan with the daemon is still faster
> while scanning the major part of the file system, compared to running
> clamscan, even if the daemon uses some swap space.
>
> Obviously, this setup is not optimal. I looked into running clamdscan
> against a service on a different system in the same network, but this seems
> not to be supported out of the box.
>
> Would it hurt to increase the timeout or make it adjustable?
>
> Dominik
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-clamav-devel/attachments/20210120/579f4f41/attachment.html>