From owner-freebsd-ports@FreeBSD.ORG Wed Jan 24 04:16:19 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 364FA16A400 for ; Wed, 24 Jan 2007 04:16:19 +0000 (UTC) (envelope-from forrie@forrie.com) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.192.81]) by mx1.freebsd.org (Postfix) with ESMTP id 22E4B13C4D5 for ; Wed, 24 Jan 2007 04:16:19 +0000 (UTC) (envelope-from forrie@forrie.com) Received: from forrie.com ([24.62.224.60]) by comcast.net (rwcrmhc11) with ESMTP id <20070124040313m1100rfqjce>; Wed, 24 Jan 2007 04:03:14 +0000 Received: from [127.0.0.1] (monster.forrie.com [192.168.1.98]) (authenticated bits=0) by forrie.com (8.13.8/8.13.8) with ESMTP id l0O42dxT049185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 23 Jan 2007 23:02:40 -0500 (EST) (envelope-from forrie@forrie.com) Message-ID: <45B6DA5A.9080704@forrie.com> Date: Tue, 23 Jan 2007 23:02:34 -0500 From: Forrest Aldrich User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.6/2481/Tue Jan 23 17:10:15 2007 on mail.forrie.com X-Virus-Status: Clean Cc: Subject: SpamAssassin (spamd) eating a lot of CPU.... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 04:16:19 -0000 Since a recent update of Spamassassin to: PORTVERSION= 3.1.7 PORTREVISION= 3 I've noticed that each email that gets scanned causes the process to eat up 80+% of the CPU time, and it's slow... I'm not really sure what changed. Likewise, when I start it up for the first time, I see: [ top output ] 49106 root 1 106 0 290M 267M RUN 0 0:17 *98.52%* perl5.8.8 I have a Dell system here, and it cranks up the fan every time a message comes in now, with the recent spamd. Curious if anyone else has had these issues, etc. The system is not otherwise active, so I'm certain it's not a resource issue (or constraint thereof). Thanks.