Bug 459954 - Default clamd conf file is broken
Summary: Default clamd conf file is broken
Keywords:
Status: CLOSED DUPLICATE of bug 430177
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: amavisd-new
Version: el5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steven Pritchard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: ActualBug
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-25 05:52 UTC by jlquinn
Modified: 2011-06-09 05:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-09 05:31:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jlquinn 2008-08-25 05:52:44 UTC
Description of problem:

/etc/clam.d/amavisd.conf has syntax errors that prevent 

Version-Release number of selected component (if applicable):

amavisd-new-2.4.5-1.el5

How reproducible:

[root@mail1 ~]# service clamd.amavisd start
Starting clamd.amavisd: ERROR: Parse error at line 2: Option LogSyslog requires boolean argument.
ERROR: Can't open/parse the config file /etc/clamd.d/amavisd.conf
                                                           [FAILED]

After fixing this option to be:

LogSyslog yes

then

[root@mail1 amavisd-new-2.4.5]# service clamd.amavisd start
Starting clamd.amavisd: ERROR: Parse error at line 14: Option FixStaleSocket requires boolean argument.
ERROR: Can't open/parse the config file /etc/clamd.d/amavisd.conf
                                                           [FAILED]

Fixing this to be:

FixStaleSocket yes

allows clamd to start correctly.


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Johan Kok 2011-06-09 05:31:08 UTC
Thank you for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 430177 ***


Note You need to log in before you can comment on or make changes to this bug.