On 2017-07-10 11:40:20 [+0200], Luca Capello wrote: > Hi there, Hi, > while debugging why the TCP socket was not responding, I discovered that > everything was fine if clamd was manually started via the CLI. And then > I found <https://bugs.debian.org/771911>. > > Please, this is becoming ridiculous: > > - clamd works as expected with *its* own configuration > - there is no documentation in /usr/share/doc/clamav-daemon about the > need to dpkg-reconfigure clamav-daemon to change parameters (and even > worse behavior) > - non-Debian configuration via manual modifications or automatic tools > (e.g. <https://forge.puppet.com/edestecd/clamav>) is not respected
so what is the problem? You want additional documentation or somehow changed behavior? You have systemd as init that means that systemd will open the TCP-socket. Initially we had socket activation but this was disabled - however it still has the socket configuration via systemd. Using dpkg-reconfigure will do the right thing and properly create /etc/systemd/system/clamav-daemon.socket.d/extend.conf with the socket information. If you run under systemd then this part of clamd.conf will be ignored. If you start this via CLI then it won't run under systemd (same goes for systemV as init) and the arguments are parsed again. > The combination of all the above factors suggests me that the severity > is higher than important, but leaving at it for now. That systemd service file is part of upstream since a few releases. You could argue if systemd's socket "feature" should be used or not or third party tools extended to the extend.conf file in systemd's case. Or the documentation updated. > Thx, bye, > Gismo / Luca Sebastian
