Correction. Apparently clamdscan doesn't have a debug mode, but -v for verbose
might help.
Best to use clamscan --debug.
-Al-
Run clamscan or clamdscan --debug. The log should be able to tell you what and
where that file is.
-Al-
On Mon, Aug 19, 2019 at 02:43 PM, Michael Newm
Run clamscan or clamdscan --debug. The log should be able to tell you what and
where that file is.
-Al-
On Mon, Aug 19, 2019 at 02:43 PM, Michael Newman via clamav-users wrote:
> I keep getting this message:
>
> "LibClamAV Warning: cli_scanxz: decompress file size exceeds limits - only
> scann
I'm currently running ClamAV in a debian docker container. I've enabled
LogSyslog in the clamd.conf and freshclam.conf files. For some reason the log
output isn't appending the app-name, procid, nor msgid to the front of the
logs. Any idea why this is? I need that metadata so my SEIM can decode
I keep getting this message:
"LibClamAV Warning: cli_scanxz: decompress file size exceeds limits - only
scanning 27262976 bytes"
I know what it means. Is there some way to find that file?
___
clamav-users mailing list
clamav-users@lists.clamav.net
ht
