[clamav-users] clamav-milter start or restart changes owner/group

[Joe Acquisto-j4]

> 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, it's about your system and the way it
> does things.  Try reading some of the the systemd 'man' pages, e.g.
> 
> man systemctl
> man systemd.socket
> man systemd.syntax
> 
> and if that doesn't help search for something like
> 
> systemctl unit files
> 
> with which you will probably need to get used to tinkering.
> 
> If you have 'locate' on your system you could also try
> 
> locate .socket | grep clam
> 
> which might find your clamav-milter systemd .socket file.

Don't I already know where the sockets are?

/var/run/clamav-milter.socket and /run/clamav-milter.socket

The "unit" files seem to be at 

/usr/lib/systemd/system/clamav-milter.service
/usr/lib/systemd/system/clamd.service

the  clamav-milter.service is quite similar to the clamd.service
which does not alter the owner or group.

[Unit]
Description=Clamav antivirus milter daemon
After=network.target clamd.service
Requires=clamd.service

[Service]
Type=forking
ExecStart=/usr/sbin/clamav-milter
; it will switch to vscan user
;User=vscan
;Group=vscan
;PrivateTmp=yes

[Install]
WantedBy=multi-user.target

 
> I admit (profess?) I much prefer to do things like this myself, rather
> than have something like systemd do it for me, but it seems to be The
> Way Of The World at the moment.
> 
> -- 
> 
> 73,
> Ged.

I'll keep at it. Maybe have a go at the opensuse support forums as well.

joe a.