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:3
Regarding the foreground option on Windows, clamd.exe remains in the foreground
regardless of the setting. This is intentional, because programs in Windows
aren't expected to background themselves. It's not normal behavior.
A daemon on Posix systems is just an ordinary program that creates a
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
