Bug 57723

Summary:	clamav - freshclam doesn't start if FRESHCLAM_LOG is not defined in /etc/conf.d/clamd
Product:	Gentoo Linux	Reporter:	Mathias Gug <mathias.gug>
Component:	[OLD] Server	Assignee:	Antivirus Team <antivirus>
Status:	RESOLVED FIXED
Severity:	normal	CC:	aross
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	patch to clamd.rc to fix FRESHCLAM_LOG handling.

Description Mathias Gug 2004-07-20 06:32:45 UTC

if FRESHCLAM_LOG is not specified in /etc/conf.d/clamd, freshclam fails to start.

Reproducible: Always
Steps to Reproduce:
1. Comment FRESHCLAM_LOG in /etc/conf.d/clamd.
2. Restart clamd.
3. freshclam is not able to start




The problem comes from the clamd init script : freshclam is always started with
-l option to specify a log file. Even if there isn't any log file defined.

Comment 1 Mathias Gug 2004-07-20 06:34:21 UTC

Created attachment 35811 [details, diff]
patch to clamd.rc to fix FRESHCLAM_LOG handling.

This patch redefines correctly FRESHCLAM_OPTS to include FRESHCLAM_LOG if it's
defined.

Comment 2 Mathias Gug 2004-07-20 06:39:11 UTC

Related information : bug 43666

Comment 3 Andrew Ross (RETIRED) gentoo-dev

2004-07-29 04:47:37 UTC

We are about to replace our current email virus scanner (McAfee) with ClamAV. Since we want to use syslog for logging, we have a particular interest in this bug.

Comment 4 Thomas Raschbacher gentoo-dev

2004-07-30 18:42:56 UTC

fixed that one today. it's in portage tree by now i think