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/pid files. This is all working well, as
far as I
can tell.
However, I've had a number of reboots recently, and after each one the following
happens:
* The clamav directory (/var/run/clamav) is deleted.
* The clamav-milter directory (/var/run/clamav-milter) is changed to owner
clmilt.
The conf files do NOT change. Therefore, I get an error (misleading, at that)
for
clamav-milter. Clamav seems to start, but does not create a socket file, and
so the
milter can't find it (and can't create its own run file in a directory it
doesn't own.
Does this make sense to anyone?
On 26.03.15 16:40, Bryan Burke wrote:
It does, in fact. On RHEL7 (and variants), /var/run is now a symlink to /run,
which is a
tmpfs, so it is always cleared on reboot.
it's the same on debian 7 and apparently other systems.
For persistent application data, you should put
things in /var/lib, e.g. /var/lib/clamav.
note that /var/run/clamav and /var/run/clamav-milter are NOT persistent and
should not be treated as such.
they are apparently created by system startup scripts, you should look
there.
I have /var/run/clamav (in fact /run/clamav) used by all: milter, freshclam and
clamd, all startup scripts create them if it does not exist (verified now),
with owner settable in /etc/default/clamav-*
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The 3 biggets disasters: Hiroshima 45, Tschernobyl 86, Windows 95
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
