From owner-freebsd-questions@FreeBSD.ORG Sat Mar 8 10:14:50 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FBA8106566B for ; Sat, 8 Mar 2008 10:14:50 +0000 (UTC) (envelope-from neil@darlow.co.uk) Received: from mtaout02-winn.ispmail.ntl.com (mtaout02-winn.ispmail.ntl.com [81.103.221.48]) by mx1.freebsd.org (Postfix) with ESMTP id BEF7A8FC1C for ; Sat, 8 Mar 2008 10:14:49 +0000 (UTC) (envelope-from neil@darlow.co.uk) Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com with ESMTP id <20080308101707.GQMW27871.mtaout02-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com> for ; Sat, 8 Mar 2008 10:17:07 +0000 Received: from router.darlow.co.uk ([80.6.42.220]) by aamtaout03-winn.ispmail.ntl.com with ESMTP id <20080308101942.MFAI26699.aamtaout03-winn.ispmail.ntl.com@router.darlow.co.uk> for ; Sat, 8 Mar 2008 10:19:42 +0000 Received: from router.darlow.co.uk (localhost [127.0.0.1]) by router.darlow.co.uk (Postfix) with ESMTP id 6A7051031B8 for ; Sat, 8 Mar 2008 10:14:38 +0000 (GMT) Received: from [192.168.0.241] (aurora.darlow.co.uk [192.168.0.241]) by router.darlow.co.uk (Postfix) with ESMTPSA id 3A8B5102EC5 for ; Sat, 8 Mar 2008 10:14:38 +0000 (GMT) Message-ID: <47D2670D.3020108@darlow.co.uk> Date: Sat, 08 Mar 2008 10:14:37 +0000 From: Neil Darlow User-Agent: Thunderbird 2.0.0.12 (X11/20080228) MIME-Version: 1.0 To: freebsd-questions@freebsd.org X-Enigmail-Version: 0.95.6 OpenPGP: id=531F9048 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamSMTP-1.9/ClamAV-0.92.1 Subject: Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Mar 2008 10:14:50 -0000 Hi, I've caught bzip2 misbehaving. The following "top" output is for compression of /var/log/messages (just over 100kB size) and it's not finished yet: 21172 root 1 118 0 11360K 8248K RUN 11:02 100.00% bzip2 Over 11 minutes, and still going, at 100% CPU. Now that's definitely not right. Anyone else seeing this? Regards, Neil Darlow