Bug 144291

Summary:	clamd : changes of /etc/conf.d/clamd are not correctly considered
Product:	Gentoo Linux	Reporter:	Toralf Förster <toralf>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED WORKSFORME
Severity:	minor
Priority:	High
Version:	2006.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Toralf Förster gentoo-dev

2006-08-18 02:24:52 UTC

During boot process clamd was started using default config:

START_CLAMD=yes
START_FRESHCLAM=yes

I decided to change these values to:

START_CLAMD=no
START_FRESHCLAM=yes

and restarted /etc/init.d/clamd. The effect is, that freshclam is restarted, whereas clamd is untouched and therefor still running. But the intention of this change is that clamd should not run.

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2006-08-18 02:51:12 UTC

How about that you stop clamd first? I don't see any bug here, the variable purpose is to check whether it should be started, and not to stop it if you already started it.

Comment 2 Toralf Förster gentoo-dev

2006-08-18 04:39:40 UTC

(In reply to comment #1)
> the variable
> purpose is to check whether it should be started, and not to stop it if you
> already started it.

Ok, under this assumption it isn't a bug.