[clamav-users] Strange behaviors about syslog on Debian

[Matus UHLAR - fantomas]

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,authpriv.none    -/var/log/syslog
>2. Set LogSyslog to false in both /etc/freshclam.conf and /etc/clamd.d/scan.conf
>
>And finally I rebooted system. Then result is that clamd didn't write
>any message to syslog and executing freshclam didin't either. To make
>sure I set LogSyslog to true and reboot again. And this time both
>clamd and freshclam wrote message to syslog.
>
>So now syslog issue is proved to be Debian specific. I don't know
>where the source of this issue lies. But anyway I'll send bug report
>to maintainer of Debian ClamAV package.

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?

-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
If Barbie is so popular, why do you have to buy her friends?