|
On 07/04/2016 06:09 PM, Sebastian
Andrzej Siewior wrote:
If you read the .socket file then you will see that one creates the socket and the .service file depends on it. Uppon start, systemd passes the socket to clamd then. I *assume* that the socket part is not started for some reason on your machines. Hi Sabastian, I have restarted the clamav-daemon.socket and the clamav-daemon.service files multiple times but /run/clamav/clamd.ctl is never created. To restart these files, I use: systemctl restart clamav-daemon.socket systemctl restart clamav-daemon Furthermore, after rebooting and/or restarting the .socket and .service files, the /run/clamav directory is never created either. I have also tried manually creating the /run/clamav directory with user=clamav and group=clamav, however, the clamd.ctl file is then never created after restarting the .socket and .service files and, after rebooting, the /run/clamav directory is not re-created either. So, for some reason, while the clamav-daemon.socket file has been run multiple times both manually and by rebooting, it never does its job to create the /run/clamav/clamd.ctl file and I have been unable to find anything in the logs to tell me why its not creating /run/clamav/clamd.ctl. What do you recommend that I do to further troubleshoot this problem? Please advise..... Thanks, Gordon |
_______________________________________________ Pkg-clamav-devel mailing list Pkg-clamav-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
