Bug 164865 - clamav doesn't start after update to 86.2-2
Summary: clamav doesn't start after update to 86.2-2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: clamav
Version: 4
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Enrico Scholz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-02 00:44 UTC by Phil Anderson
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-08-03 00:39:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Phil Anderson 2005-08-02 00:44:32 UTC
Description of problem:
When starting clamav after updating to 86.2-2, the following error is printed to
the console, and clamav doesn't start.  Note that --timeout is not listed in
/etc/sysconfig/clamav-milter

/usr/sbin/clamav-milter: --timeout must not be given if --external is not given


Version-Release number of selected component (if applicable):
86.2-2 and 86.2-3.  Downgrading to 86.1-2 fixes the problem.

How reproducible:
100%

Here is the contents of my /etc/sysconfig/clamav-milter:
## The '-blo' options might be usefully here -- especially for testing; see
## "man 8 clamav-milter" for further options
CLAMAV_FLAGS='-q -l -A --max-children=2 -c /etc/clamd.d/milter.conf
local:/var/run/clamav-milter/clamav.sock'
CLAMAV_USER='clamilt'

Comment 1 Phil Anderson 2005-08-03 00:39:00 UTC
Upgrade to 0.86.2-4 fixes this:

* Sat Jul 30 2005 Enrico Scholz <enrico.scholz.de> - 0.86.2-4

- [milter] create the milter-logfile in the %post scriptlet
- [milter] reverted the change of the default child_timeout value; it
  was set to 5 minutes in 0.86.2 which conflicts with the internal
  mode where a timeout must not be set. So, the clamav-milter would
  not run with the default configuration



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