I have both clamd and clamav-milter installed on my CentOS 7 machine. For ease
of use,
I've got bth configured to use one id, 'clamav'. This means I use two different
directories, /var/run/clamav and /var/run/clamav-milter, owned by user clamav
and set to
permissions 711, to hold the socket/pi
I had the same problem with clammsmtp recently. Look at the init.d start
script of the milter. Look for a chown clmit /var/run/clmit line and change
it to chown clamav
Am 26.03.2015 20:46 schrieb "Don Levey" :
> I can't find a logical explanation for this, so I thought I'd ask here.
>
> I have
On 3/26/2015 16:40, Bryan Burke wrote:
>> I have both clamd and clamav-milter installed on my CentOS 7 machine. For
>> ease of use,
>> I've got bth configured to use one id, 'clamav'. This means I use two
>> different
>> directories, /var/run/clamav and /var/run/clamav-milter, owned by user
>>
> I have both clamd and clamav-milter installed on my CentOS 7 machine. For
> ease of use,
> I've got bth configured to use one id, 'clamav'. This means I use two
> different
> directories, /var/run/clamav and /var/run/clamav-milter, owned by user clamav
> and set to
> permissions 711, to hold
I can't find a logical explanation for this, so I thought I'd ask here.
I have both clamd and clamav-milter installed on my CentOS 7 machine.
For ease of use, I've got bth configured to use one id, 'clamav'. This
means I use two different directories, /var/run/clamav and
/var/run/clamav-milter, o
