| Summary: | amavisd doesn't start in fc15 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ian Donaldson <iand> |
| Component: | amavisd-new | Assignee: | Steven Pritchard <steve> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | iand, perl-devel, steve, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-12 22:55:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
This appears to be a duplicate of bug 696725. Those directories should now be created on boot. There's an amavisd-new.conf in /etc/tmpfiles.d for that. In my testing, it works fine. My apologies; this was a bug report I forgot to file when I noticed the issue a few weeks back (with amavisd-new-2.6.4-3.fc15.noarch). It seems the fix *has* been applied to the version I listed in the report and I've taken my kludge away and retested; its indeed fixed in amavisd-new-2.6.6-1.fc15.noarch I'll close this. |
Description of problem: amavisd doesn't start at boot as /var/run/amavisd as installed by the rpm doesn't exist after reboot as /var/run is a tmpfs in fc15 Version-Release number of selected component (if applicable): amavisd-new-2.6.6-1.fc15.noarch How reproducible: 100% Steps to Reproduce: 1. chkconfig amavisd on; then configure it; reboot 2. 3. Actual results: ps -ef|grep amavisd shows it isn't running Expected results: running Additional info: $ rpm -ql amavisd-new |grep /var/run /var/run/amavisd /var/run/clamd.amavisd My workaround was to add an additional rc script run before amavisd -- $ ll /etc/*.d/*amavisd_kludge -r-xr-xr-x. 1 root root 366 Sep 14 08:57 /etc/init.d/amavisd_kludge -r-xr-xr-x. 1 root root 366 Sep 14 08:57 /etc/rc3.d/S77amavisd_kludge $ cat /etc/init.d/amavisd_kludge #! /bin/sh if [ -d /var/run/amavisd ] then : else mkdir /var/run/amavisd chown amavis:amavis /var/run/amavisd chmod 755 /var/run/amavisd restorecon -Rv /var/run/amavisd fi $ -- but this should probably be added to the /etc/init.d/amavisd script. In my situation I didn't require /var/run/clamd.amavisd to exist as my clamd.pid is configured to be in /var/run/amavisd/clamd.pid but for completeness the amavisd startup script probably should also create /var/run/clamd.amavisd