Red Hat Bugzilla – Bug 790042
clamav+systemd=Can't create temporary directory ERROR
Last modified: 2012-02-28 03:58:51 EST
clamav's sysv amavisd-new service does not work anymore
/etc/init.d/clamd.amavisd: line 7: /usr/share/clamav/clamd-wrapper: No such file or directory
I figured it was a good time to switch to the systemd unit, and indeed it starts up fine
However it seems to have problems creating temporary files
Can't create temporary directory ERROR
Maybe the systemd clamav unit needs some more magic to work with systemd's PrivateTmp feature?
(clamav amavisd conf taken from the amavisd-new package)
Version-Release number of selected component (if applicable):
fwiw, the clamd-wrapper script is now in the clamav-server-sysvinit package (which is going to die in the midterm).
Can you point me to the mentioned systemd unit please? amavisd-new git does not contain a such one.
I am in doubt that your problem is caused by PrivateTmp, because this affects /tmp only, not /var/spool/... Nevertheless, you can verify this by disabling PrivateTmp in the systemd unit (either clamd@.service, or in your clamd@<instance>.service file).
(In reply to comment #1)
> fwiw, the clamd-wrapper script is now in the clamav-server-sysvinit package
> (which is going to die in the midterm).
That breaks amavid as it does not depend on this new package (but should move to systemd anyway → bug #789571)
> Can you point me to the mentioned systemd unit please? amavisd-new git does not
> contain a such one.
I just used the one in clamav systemd
systemctl start firstname.lastname@example.org (IIRC) and it picked up the clamav config file shipped with the amavisd-new packages
ln -sf /lib/systemd/system/clamd@.service
Only problems are those new tmp files errors (that didn't happen with the old sysv script): maybe it's the same as bug #790522 ?
and the pid file instruction in the amavisd-new config (is it necessary with systemd? Selinux does not like it: bug #789580)
is this fixed by 790522#c19 ?
Creation of the pidfile can/should be avoided unless amavisd or system monitoring needs it.
(In reply to comment #3)
> is this fixed by 790522#c19 ?
> Creation of the pidfile can/should be avoided unless amavisd or system
> monitoring needs it.
the temporary file creation is indeed fixed by the new systemd
So, if you confirm there is no need to create the pid file, I should just ask the amavisd maintainer to remove the pid directive and use the generic clamav systemd unit, right?
*** This bug has been marked as a duplicate of bug 790522 ***