[clamav-users] Clamd Socket Occupied

[Reindl Harald]

Am 05.12.2017 um 19:34 schrieb Colony.three:
>> Am 05.12.2017 um 08:13 schrieb Colony.three:
>>
>>> As Red Hat hasn't solved the problem of unix:sockets, I had to make my own systemd files. But there's a little problem.
>>>
>>> clamd.socket
>>>
>>> [Unit]
>>> Description=Socket for Clam AntiVirus userspace daemon
>>> Documentation=man:clamd(8) man:clamd.conf(5) http://www.clamav.net/lang/en/doc/
>>> [Socket]
>>> ListenStream=/run/clamav/clamd.sock
>>>
>>> this is a terrible idea because the daemon itself needs to support this
>>> active - there is no reason for a systemd .socket file at all!
>>>
>>> just make a proper clamd unit and ensure proper permissions
> 
> It would be dynamite if the daemon did in fact create the directory for its socket.  Unfortunately it does not.  Why do you think I went to all this trouble?

i don't konw because i have two clamd instances on Redhat systems, did 
read the basic manpages as well as 
https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html

i can only tell you that clamd.socket won't solve any problem