ClamAV constantly failing

[Jason Voorhees]

Well, not, but the current PID is saved in /var/run/MailScanner:

[root at mail ~]# ps -ef | grep -w MailScanner | grep -v grep
postfix   4393     1  0 Apr03 ?        00:00:00 MailScanner: starting child
postfix   5766  4393  0 15:54 ?        00:00:01 MailScanner: waiting
for messages
postfix  25310  4393  0 15:29 ?        00:00:01 MailScanner: waiting
for messages
[root at mail ~]# cat /var/run/MailScanner.pid
4393

What's does MailScanner logs look like when it's unable to find/write
the current PID? Maybe I can look for it to verify if it's really
failing by this reason.

On Tue, Apr 12, 2016 at 4:16 PM, Kevin Miller <kevin.miller at juneau.org> wrote:
> Is /var/run writable by MailScanner?
>
> ...Kevin
> --
> Kevin Miller
> Network/email Administrator, CBJ MIS Dept.
> 155 South Seward Street
> Juneau, Alaska 99801
> Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357
>
>
> -----Original Message-----
> From: MailScanner [mailto:mailscanner-bounces+kevin.miller=juneau.org at lists.mailscanner.info] On Behalf Of Jason Voorhees
> Sent: Tuesday, April 12, 2016 11:31 AM
> To: MailScanner Discussion
> Subject: Re: ClamAV constantly failing
>
> Hi, thanks for replying... It's already set to /var/run/MailScanner.pid
>
> What else could I try?
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/listinfo/mailscanner
>