[Bug 863069] New: amavisd.service fails to start because required default folders are missing

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=863069

            Bug ID: 863069
        QA Contact: extras-qa at fedoraproject.org
          Severity: unspecified
           Version: 17
          Priority: unspecified
                CC: kanarip at kanarip.com,
                    perl-devel at lists.fedoraproject.org, steve at silug.org
          Assignee: steve at silug.org
           Summary: amavisd.service fails to start because required
                    default folders are missing
        Regression: ---
      Story Points: ---
    Classification: Fedora
                OS: Unspecified
          Reporter: sexynaya2010 at hotmail.com
              Type: Bug
     Documentation: ---
          Hardware: Unspecified
        Mount Type: ---
            Status: NEW
         Component: amavisd-new
           Product: Fedora

Description of problem:
There are some default folder locations specified in the config file that don't
get created when amavisd-new is installed.  The program fails to start because
of it.

For example, this message gets printed to the log file when trying to start the
service:
amavis[5461]: (!)Net::Server: 2012/10/04-04:35:06 Couldn't open pid file
"/var/run/amavisd/amavisd.pid" [No such file or directory].\n\n  at line 318 in
fil...Net/Server.pm

In order to make amavisd.service start correctly, I had to do the following:
mkdir /var/spool/amavisd/var
mkdir /var/run/amavisd/
chown -R amavis:amavis /var/spool/amavisd/var
chmod 700 /var/spool/amavisd/var
chown -R amavis:amavis /var/run/amavisd/

After that, everything worked as expected.

Version-Release number of selected component (if applicable):
amavisd-new-2.6.6-2.fc17.noarch

How reproducible:
Always

Steps to Reproduce:
1. yum install amavisd-new
2. systemctl start amavisd.service
3.

Actual results:
Fails to start

Expected results:
Starts using default config file

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.