This problem sounds very familiar...though on Linux....
Clamd can take VERY long to load it's signatures,
Try increasing your ServicesPipeTimeout to exagerated 600 sec to see if
it fully loads.
If that works you may want to lower values till you feel comfortable
with the length.
On 7/5/19 6:39 PM, lists--- via clamav-users wrote:
I am trying to set up a Windows service running clamd.exe. At first I
was running into a timeout issue whereby it would take too long to
start, so the service manager would kill it. So I increased
the value of ServicesPipeTimeout to 60 seconds. That took care of that
problem.
Now I can see in the clamd.log that the process finishes starting up,
but Windows doesn't
recognize it. So once the 60 seconds comes around, it kills the
clamd.exe process. I have tried
both foreground and daemonizing the clamd.exe process, both with the
same result.
Am I missing something?
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
