Please don't hijack a thread to report a bug or request an improvement. A new
thread for new discussion topic is always great.
Please also be careful in your phrasing. ClamAV's docker support was 99% the
work of a kind-hearted community member. Mocking the current design isn't
helpful. I do see
On Thu, 17 Feb 2022 14:08:45 +0100
An Schall via clamav-users wrote:
> When using clamdscan, I would like to have verbose output logged to a
> file. Specifically, the timestamp, file path and file name as well as
> the scan results should be logged to a specified file.
>
> In comparison, clamsca
Hi there,
On Thu, 17 Feb 2022, An Schall via clamav-users wrote:
When using clamdscan, I would like to have verbose output logged to a
file. Specifically, the timestamp, file path and file name as well as
the scan results should be logged to a specified file.
In comparison, clamscan outputs th
When using clamdscan, I would like to have verbose output logged to a
file. Specifically, the timestamp, file path and file name as well as
the scan results should be logged to a specified file.
In comparison, clamscan outputs this information to STDOUT per default
and I could simply pipe it to "t
