On Wed, 2011-07-20 at 16:11 +0100, Arthur Dent wrote:

> For the benefit of the archives this is what now works for me:
> 
> #============8<===================================================
> # In the definitions section:
> CLAMD_PIDDIR=/var/run/clamd.${CLAMD_SERVICE}
> 
> # and in the "start" stanza:
> 
>  if [ ! -d $CLAMD_PIDDIR ] ; then
>          mkdir $CLAMD_PIDDIR && chown clamd:clamd $CLAMD_PIDDIR
>       fi
> #============8<===================================================

For those who aren't following the bug
https://bugzilla.redhat.com/show_bug.cgi?id=723544 Apparently the
correct solution to the problem of /var/run now being tempfs (and
therefore wiped clean with each reboot) is to create a /etc/tmpfiles.d
file with instructions on how to create the directory with the
appropriate permissions. This simply involves (for me) creating
a /etc/tmpfiles.d/clamd.conf file with the following line in it:

d /var/run/clamd.clamd 0700 clamd clamd -

At reboot the directory /var/run/clamd.clamd/ is then created with 0700
permissions and clamd:clamd ownership. The clamd package will then start
properly.

I hope that helps anyone else suffering the same problem.

Mark


Attachment: signature.asc
Description: This is a digitally signed message part

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Reply via email to