Re: [clamav-users] clamscan (NOT clamdscan) log file setup in *.conf file?

Note too that clamscan runs as the >current user, so it may not see all you wish nor log where you wish, >based on >file system permissions. It also has to load the entire signature set >each time >it is run. > >dp > >On 11/16/16 11:07 AM, Fouts, Christopher wrote:

[clamav-users] clamscan (NOT clamdscan) log file setup in *.conf file?

The docs show the following example when running clamscan (NOT clamdscan) $ clamscan –r –l scan.txt /some_path How can I configure the log file in the /etc/clamd.d/scan.conf file for clamscan, not for clamdscan? I see # Uncomment this option to enable logging. # LogFile must be writable for

Re: [clamav-users] ClamAV RPM vs source code installation

Thanks all. This thread helped. Chris On 11/15/16, 12:58 PM, "clamav-users on behalf of Reindl Harald" wrote: > > >Am 15.11.2016 um 18:39 schrieb Dennis Peterson: >> Hmm - just noticed my asterisk is missing. Should be:

Re: [clamav-users] ClamAV RPM vs source code installation

Those utilities are clamd and freshclam. (Outlook spell-uncorrected them.) Chris On 11/15/16, 10:31 AM, "clamav-users on behalf of Fouts, Christopher" <clamav-users-boun...@lists.clamav.net on behalf of christopher.fo...@teradata.com> wrote: >How come the Centos RPM (v0.99.

[clamav-users] ClamAV RPM vs source code installation

How come the Centos RPM (v0.99.2) does not install everything that the compiled source code does? For example, I don’t see clams, fresh clam, and the configuration in /etc/clamav.conf, Where do I get this other utilities via RPM? Thanks, chris ___