Re: clamav-milter's pid

[Mike Pepe]

Martin Pala wrote:
> The cause of the problem may be in pidfile ... in your previous mail you 
> compared the contents of /var/run/clamav/clamav-milter.pid.fixed file 
> with the running process:
>
> --8<--
> # cat /var/run/clamav/clamav-milter.pid.fixed
> 12781
> # ps -ef | grep clamav-milter
> clamilt  12781     1  0 16:19 ?        00:00:00 /usr/sbin/clamav-milter 
> --quiet --external --dont-wait --force-scan --dont-log-clean 
> --server=localhost --pidfile=/var/run/clamav/clamav-milter.pid 
> local:/var/run/clamav/clamav-milter.sock
> --8<--
>
> however, monit was configured to check the pid which is stored in 
> /var/run/clamav/clamav-milter.pid (containg the incompatible format):
>
> --8<--
> Process Name          = clamav-milter
>  Group                = milter
>  Pid file             = /var/run/clamav/clamav-milter.pid
>  ...
> --8<--

Well, that was part of it. I had it that way before and it still didn't 
work, but, now it does (?)

Not sure what happened, but its nice that it works!

thanks Martin

-Mike