From: Matus UHLAR - fantomas
I use Debian 9 (i386) with sysvinit, no logging to syslog is done.
LogSyslog is set to false everywhere.
I don't see any init (only init.d) files for clamd. Do you see any on
your system?
On 25.11.18 01:31, Yasuhiro KIMURA wrote:
Though I use Debian 9 (x86_64) w
From: Matus UHLAR - fantomas
Subject: Re: [clamav-users] Strange behaviors about syslog on Debian
Date: Sat, 24 Nov 2018 17:06:02 +0100
> I use Debian 9 (i386) with sysvinit, no logging to syslog is done.
> LogSyslog is set to false everywhere.
>
> I don't see any init (only
On 25.11.18 00:52, Yasuhiro KIMURA wrote:
I set up CentOS 7.x environment with following conditions.
* CentOS 7.5.1804
* ClamAV 0.100.2 from EPEL(Extra Packages for Enterprise Linux by
Fedora Project)
Next I made following changes.
1. Add following line in /etc/rsyslog.conf
*.*;auth,authpr
From: Yasuhiro KIMURA
Subject: Re: [clamav-users] Strange behaviors about syslog on Debian
Date: Sat, 24 Nov 2018 18:55:05 +0900 (JST)
> And I'm going to setup CentOS 7.x from now and will check how it
> behaves about syslog issue.
I set up CentOS 7.x environment with following
From: Yasuhiro KIMURA
Subject: Re: [clamav-users] Strange behaviors about syslog on Debian
Date: Fri, 16 Nov 2018 02:31:55 +0900 (JST)
> And next I'll setup 7.x and test on it. But I'm away this weekend. So
> I'll do it and report result next week.
Sorry for delay. Hardwar
Hello Scott, Thank you for reply.
From: Scott Kitterman
Subject: Re: [clamav-users] Strange behaviors about syslog on Debian
Date: Wed, 14 Nov 2018 02:08:12 +
> Assuming you haven't made an effort to select sys v init on the Debian
> system, it's running using syst
On November 13, 2018 10:28:27 PM UTC, Yasuhiro KIMURA wrote:
>Hello,
>
>I use ClamAV 0.100.2 on Debian 9.6. Everything works fine about virus
>scan. But when seeing syslog I found 2 strange behaviors.
>
>1. Message is written to syslog even if LogSyslog is false.
>
>On Debian LogSyslog is set t
Hello,
I use ClamAV 0.100.2 on Debian 9.6. Everything works fine about virus
scan. But when seeing syslog I found 2 strange behaviors.
1. Message is written to syslog even if LogSyslog is false.
On Debian LogSyslog is set to false in both clamd.conf and
frashclam.conf. But there are messages fro
