From owner-freebsd-questions@FreeBSD.ORG Mon Nov 26 19:58:46 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4BAB16A47A for ; Mon, 26 Nov 2007 19:58:46 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (muon.bluestop.org [IPv6:2001:41c8:1:548a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5344A13C458 for ; Mon, 26 Nov 2007 19:58:46 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from [IPv6:2a01:348:10f:1::7] (unknown [IPv6:2a01:348:10f:1::7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id B72B2C4001; Mon, 26 Nov 2007 19:58:44 +0000 (GMT) Message-ID: <474B2571.7090801@cran.org.uk> Date: Mon, 26 Nov 2007 19:58:41 +0000 From: Bruce Cran User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Giorgos Keramidas References: <20071126095833.GA6422@submonkey.net> <20071126112106.GC2283@kobe.laptop> In-Reply-To: <20071126112106.GC2283@kobe.laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Ceri Davies , questions@freebsd.org Subject: Re: Strange kernel log message 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: Mon, 26 Nov 2007 19:58:46 -0000 Giorgos Keramidas wrote: > On 2007-11-26 09:58, Ceri Davies wrote: > >> So I have this in my security run output: >> kernel log messages: >> +++ /tmp/security.hLYJI0kF Sun Nov 25 03:01:02 2007 >> +<<<<222>2>>>NNNMNMMIII M III SIISAS SAAA 3 303,020,0 ,, EE IEIIESSSAIAA S A f ffffff >> + >> + >> +f >> >> WTF now? >> >> I'm not sure if that's a real kernel message that got garbled or whether >> I should be worried about naughtiness. >> > > It looks like multiple messages overlapping each other. Removing 3 > characters every 4 bytes in the output produces things which seem > vaguely recognizable: > > <22NNI II A ,,,EISA fff > <<2>NMI SS 300 ISAAfff > > There's a sysctl option which you can tweak to make this less likely to > happen, but I am not sure about its name. Our console gurus can help > you track it down and tune its value :) > > The kernel option I've seen mentioned before to at least make this less common is: options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed. -- Bruce