Problem with security log

Andriy Gapon avg at
Thu Oct 14 12:59:10 UTC 2010

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 <freebsd at> 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:

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

More information about the freebsd-stable mailing list