Am 07.08.2016 um 17:04 schrieb Alan Stern:
On Sun, 7 Aug 2016, Chris wrote:On Sun, 2016-08-07 at 10:49 +0200, Tobi wrote:It might a systemd issue. Have you tried to start clamd by calling it directly on cli? Does it create the socket then? Cheers tobiI've tried that lots of times Tobi, however, it still doesn't create it: chris@localhost:~$ sudo service clamav-daemon stop [ - ] clamav- daemon chris@localhost:~$ sudo service clamav-daemon start [ + ] clamav- daemonWhen systemd is installed, the "service" command is redirected to invoke systemctl. To truly bypass systemd you would need to do something like "sudo /etc/init.d/clamav-daemon stop", etc.The 'clamd.socket' file should be between these two but it's not: -rw-r--r-- 1 clamav clamav 446464 Jun 23 11:40 bytecode.cld -rw-r--r-- 1 clamav clamav 82 Jul 13 14:44 crdfam.clamav.hdbThis also could be caused by SELinux. It can prevent files from being created even when all the permission settings are okay. Have you checked the system logs for audit violations? Also, have you checked clamd's log file?
that and and on a smart setup /var/lib/clamd has a *readonly namespace* in the systemd-unit because it's asking for troubles let the software which deals by definiton with malicious code manipulate it's own signature files
hence lockfiles, pidfiles and sicketfiles belong to /run
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
