Clamd daemon not detected when running as a service.
it at festa.bg
Tue Feb 4 11:34:56 UTC 2020
/etc/systemd/system/clamd at .service
add "TimeoutStartSec=360" like below if 360 seconds are anough for clamd
to load signatures and open sockets at startup
Type = forking
ExecStart = /usr/sbin/clamd -c /etc/clamd.d/%i.conf
Restart = on-failure
На 04.02.2020 в 08:25, Pramod Daya via MailScanner написа:
> Hi Folks,
> Clamd (101.4-1) running as a service does not get detected by
> MailScanner (5.0.3-7) After starting the service (on Centos 7) It
> takes quite a long time for clamd to become operational (up to a
> couple of minutes) before you can connect to the socket (I have it
> configured on port 3310).
> If I then restart MailScanner, then clamd is not detected, and
> Mailscanner uses clamav, which of course overloads the server. If I
> start clamd from the command line, then Mailscanner detects clamd, and
> all is well.
> Any/all advice would be very welcome. I know that the config file is
> being read, because I change other parameters, like enabling
> debugging, and it gets interpreted.
> Thank you,
"Феста Холдинг" АД
бул. "Вл. Варненчик" 48
9000 гр. Варна
тел.: +359 52 669137
GSM: +359 888 669137
Fax: +359 52 669110
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MailScanner