From owner-freebsd-stable@FreeBSD.ORG Thu Oct 14 12:59:10 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 70431106564A for ; Thu, 14 Oct 2010 12:59:10 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B2AB38FC18 for ; Thu, 14 Oct 2010 12:59:09 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA03541; Thu, 14 Oct 2010 15:58:56 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4CB6FE90.8010203@icyb.net.ua> Date: Thu, 14 Oct 2010 15:58:56 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Jeremy Chadwick References: <20101013081758.GA52870@icarus.home.lan> <20101014134638.c0feace3.torfinn.ingolfsen@broadpark.no> <20101014120748.GA82271@icarus.home.lan> In-Reply-To: <20101014120748.GA82271@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Torfinn Ingolfsen , 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:59:10 -0000 on 14/10/2010 15:07 Jeremy Chadwick said the following: > 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 > Just to clarify. This still talks about printing to console. During panics and traps. Because of one logical message being printed with multiple printf calls. And so on. But still this is about printing to console. Which is related. Which is a problem too. The other problem is that all writing to message buffer is always done character by character only. Even when writing special tokens like log levels. -- Andriy Gapon