Bug 75607 - clamav: some practical ideas
Summary: clamav: some practical ideas
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Yar Tikhiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-29 13:50 UTC by Yar Tikhiy
Modified: 2005-01-12 18:30 UTC (History)
1 user (show)

See Also:

Attachments
file.diff (4.82 KB, patch)
2004-12-29 13:50 UTC, Yar Tikhiy 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yar Tikhiy freebsd_committer freebsd_triage 2004-12-29 13:50:14 UTC 
	1. Deinstalling clamav while clamav-milter is active won't
	go beyond trying to stop clamd, which isn't going to exit
	on a signal until all its clients disconnect.  I'd rather
	add an @unexec to stop clamav-milter before clamd if the
	former is active.

	2. Clamd should start before freshclam and clamav-milter IMHO.
	This can be achieved by means of rcorder(8) keywords.

	3. Clamav-milter won't write its pidfile unlike the rest of
	clamav daemons.  This can be fixed easily.

	Thanks!

Fix: To Rob Evers: I can commit this patch if you like my ideas.
Comment 1 rob 2005-01-10 18:33:11 UTC 
Sorry for the late reply,

Could you commit this it looks fine.

Rob Evers
Comment 2 Yar Tikhiy 2005-01-12 18:28:51 UTC 
On Mon, Jan 10, 2005 at 07:33:11PM +0100, Rob Evers wrote:
> 
> Could you commit this it looks fine.

I've just incorporated the changes to the clamav and clamav-devel ports.
A part of them already was in clamav-devel, so I added the rest, too.
Thank you!

-- 
Yar
Comment 3 Yar Tikhiy freebsd_committer freebsd_triage 2005-01-12 18:29:16 UTC 
State Changed
From-To: open->closed

Committed, thanks!
Comment 4 Yar Tikhiy freebsd_committer freebsd_triage 2005-01-12 18:29:16 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->yar

Committed, thanks!