Citeren "G.W. Haywood via clamav-users" :
This is not to say that it can't be worked around by the configuration
of clamav-milter directly, of course it can, but if he does that he'll
be confused by the next update, when it bleats about files having been
changed from the versions which were dist
> Citeren Joe Acquisto-j4 :
>
Citeren "G.W. Haywood via clamav-users" :
> Hi there,
>
> On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
>
>> Seems starting or restarting clamav-milter (systemctl restart
>> clamav-milter.service)
>> changes owner and group of /va
Citeren Joe Acquisto-j4 :
Citeren "G.W. Haywood via clamav-users" :
Hi there,
On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
Seems starting or restarting clamav-milter (systemctl restart
clamav-milter.service)
changes owner and group of /var/run/clamav-milter.socket to root
which make the
sock
>
>>> Citeren "G.W. Haywood via clamav-users" :
>>>
Hi there,
On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
> Seems starting or restarting clamav-milter (systemctl restart
> clamav-milter.service)
> changes owner and group of /var/run/clamav-milter.socket to roo
Hi there,
On Tue, 23 Feb 2021, Arjen de Korte via clamav-users wrote:
Citeren "G.W. Haywood via clamav-users" :
This isn't about clamav-milter, it's about your system and the way it
does things. Try reading some of the the systemd 'man' pages, e.g.
It *is* about clamav-miiter. The owner an
>> Citeren "G.W. Haywood via clamav-users" :
>>
>>> Hi there,
>>>
>>> On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
>>>
Seems starting or restarting clamav-milter (systemctl restart
clamav-milter.service)
changes owner and group of /var/run/clamav-milter.socket to root
whi
> Citeren "G.W. Haywood via clamav-users" :
>
>> Hi there,
>>
>> On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
>>
>>> Seems starting or restarting clamav-milter (systemctl restart
>>> clamav-milter.service)
>>> changes owner and group of /var/run/clamav-milter.socket to root
>>> which make the
Citeren "G.W. Haywood via clamav-users" :
Hi there,
On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
Seems starting or restarting clamav-milter (systemctl restart
clamav-milter.service)
changes owner and group of /var/run/clamav-milter.socket to root
which make the
socket inaccessible to postf
> Hi there,
>
> On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
>
>> Seems starting or restarting clamav-milter (systemctl restart
> clamav-milter.service)
>> changes owner and group of /var/run/clamav-milter.socket to root which make
> the
>> socket inaccessible to postfix (at least).
>
> This
Hi there,
On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
Seems starting or restarting clamav-milter (systemctl restart
clamav-milter.service)
changes owner and group of /var/run/clamav-milter.socket to root which make the
socket inaccessible to postfix (at least).
This isn't about clamav-milter
Seems starting or restarting clamav-milter (systemctl restart
clamav-milter.service)
changes owner and group of /var/run/clamav-milter.socket to root which make the
socket inaccessible to postfix (at least).
I found some reference to a similar concern dated 2009 and 2013.
Does not appear rel
11 matches
Mail list logo
