From owner-freebsd-stable@FreeBSD.ORG Thu Oct 14 12:07:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 067FE1065694 for ; Thu, 14 Oct 2010 12:07:51 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by mx1.freebsd.org (Postfix) with ESMTP id E014E8FC19 for ; Thu, 14 Oct 2010 12:07:50 +0000 (UTC) Received: from omta11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by qmta15.emeryville.ca.mail.comcast.net with comcast id Jbl61f0030mlR8UAFc7qo3; Thu, 14 Oct 2010 12:07:50 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta11.emeryville.ca.mail.comcast.net with comcast id Jc7p1f0033LrwQ28Xc7p8S; Thu, 14 Oct 2010 12:07:50 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id EBD569B418; Thu, 14 Oct 2010 05:07:48 -0700 (PDT) Date: Thu, 14 Oct 2010 05:07:48 -0700 From: Jeremy Chadwick To: Torfinn Ingolfsen Message-ID: <20101014120748.GA82271@icarus.home.lan> References: <20101013081758.GA52870@icarus.home.lan> <20101014134638.c0feace3.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101014134638.c0feace3.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: Problem with security log X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2010 12:07:51 -0000 On Thu, Oct 14, 2010 at 01:46:38PM +0200, Torfinn Ingolfsen wrote: > On Wed, 13 Oct 2010 01:17:58 -0700 > Jeremy Chadwick wrote: > > > There isn't a 100% reliable way to get rid of this problem. I've been > > harping about this for years (sorry to sound like a jerk, but this > > really is a major problem that keeps coming up and annoys users/admins > > to no end. > > Or the problem might not be so major, it only shows up on the mailing > lists about every six months. So maybe those who have the problem learns > how to live with it. > If it was a major problem, the mailing lists would be flooded. > > Just my 0.02 eurocents. I respect your opinion, and you're right, it doesn't come up too often. But I classify this problem as high/severe because it makes a mess of things at the worst time possible -- situations where you absolutely need reliable output due to the nature of the problem you're dealing with (debugging a kernel, figuring out how/why something broke in the kernel, devices complaining about issues, disks reporting problems, etc.). Last time I think this came up was in July or August, and prior to that, March (at least on the lists I'm sub'd to). John Baldwin had some useful things to say back in March about the issue. Relevant thread posts: http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg70744.html http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg70745.html http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg70746.html -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |