[clamav-users] clamdscan: Output detailed scan results to STDOUT or to configurable file?

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

Re: [clamav-users] clamdscan: Output detailed scan results to STDOUT or to configurable file?

5:39 2022 -> /home/foo/lynis/include/tests_kernel: OK My aim is to log the per-file information to a configurable log file. Maybe my undertaking becomes a bit clearer now. Thanks Am Do., 17. Feb. 2022 um 18:17 Uhr schrieb Paul Kosinski via clamav-users : > > On Thu, 17 Feb 2022 14:08

Re: [clamav-users] clamdscan: Output detailed scan results to STDOUT or to configurable file?

logging in clamdscan. Thanks anyway! Am Mo., 21. Feb. 2022 um 10:34 Uhr schrieb G.W. Haywood via clamav-users : > > Hi there, > > On Mon, 21 Feb 2022, An Schall via clamav-users wrote: > > > ... my issue is that when scanning folders recursively with > > clamdscan, I merely recei

Re: [clamav-users] clamdscan: Output detailed scan results to STDOUT or to configurable file?

easy to simply pipe the verbose output to tee and append the custom log file. Now I have to use "cat" and it seems like this introduces some error. Am Mo., 21. Feb. 2022 um 11:23 Uhr schrieb G.W. Haywood via clamav-users : > > Hi there, > > On Mon, 21 Feb 2022, An Schall

[clamav-users] Support for GPFS / real-time antivirus checks

Hi all, we have a server operating RHEL 6.x and which is using GPFS as a file system. We process high volume data on this server and are evaluating whether clamAV / clamd is a feasible solution to run AV scans against the processed data. As I could not find an official page that lists features /

[clamav-users] clamav "Can't unlink file ERROR"

Hi all, we are trying to get clamscan / clamdscan functional on a RHEL with GPFS as a filesystem. We are using clamAV 0.104.2. On a different test machine everything works like a charm. However, on this specific RHEL machine, we get the following errors: # clamdscan -v --config-file=/etc/clamav/c

Re: [clamav-users] clamav "Can't unlink file ERROR"

solution that was interfering with the operations of clamAV. Thanks again, An Am Di., 17. Mai 2022 um 13:16 Uhr schrieb G.W. Haywood via clamav-users : > > Hi there, > > On Tue, 17 May 2022, An Schall via clamav-users wrote: > > > we are trying to get clamscan / clamdscan func

[clamav-users] Can't access file ERROR - clamdscan - 0.103.7-1

Hi all, we do have 2 workstations running RHEL 8 and clamav / clamd using an identical software stack / configuration. In particular we integrate the clamav packages via the RHEL EPEL repos. So far we have been using 0.103.6-1.el8 without any issues. We have started upgrading to 0.103.7-1.el8 on o

Re: [clamav-users] Can't access file ERROR - clamdscan - 0.103.7-1

irst escalating privileges via "sudo su" and then running clamdscan against a folder within the home directory of the user from which the privileges were escalated (i.e. foo), we receive the following error: [root@epp-3o-w1 av-scans]# clamdscan -v -c /etc/clamd.d/scan.conf /home/foo/test/ /

Re: [clamav-users] Can't access file ERROR - clamdscan - 0.103.7-1

to receive some debugging information. Using the additional information I was able to pin-point the issue. Best, André Am Mo., 7. Nov. 2022 um 18:02 Uhr schrieb G.W. Haywood via clamav-users : > > Hello again, > > On Mon, 7 Nov 2022, An Schall via clamav-users wrote: > > > the comm