Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 11 Apr 2002 10:55:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 11 Apr 2002 10:55:03 -0400 Received: from www.m3.polymtl.ca ([132.207.4.60]:40455 "HELO m3.polymtl.ca") by vger.kernel.org with SMTP id ; Thu, 11 Apr 2002 10:55:02 -0400 To: Brian Beattie Cc: linux-kernel@vger.kernel.org, Martin@m3.polymtl.ca, "Martin.Bligh@us.ibm.com" , Tony.P.Lee@nokia.com, kessler@us.ibm.com, alan@lxorguk.ukuu.org.uk, Dave Jones , karym@opersys.com, lmcmpou@lmc.ericsson.se, lmcleve@lmc.ericsson.se Subject: Re: Event logging vs enhancing printk In-Reply-To: <1018385394.7923.26.camel@w-beattie1> From: Michel Dagenais Date: 11 Apr 2002 11:11:00 -0400 Message-ID: Lines: 24 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > It would be easier, to fix the printk's, than to put evlogging into any > particular piece of the kernel. Fine, let's call evlog "an enhanced printk" and discuss the specific technical details of the proposition. > Evlog side-by-side with printk adds significat bloat. Whenever you change/enhance such things you may need coexistance for a while. However this is configurable, and to a certain extent temporary, bloat. > > - Structured data events for which it is easier to apply filtering, querying, > > analysis and detection tools. > > this is a post processing problem. ... > What I hear you asking for, is to make it more of > the kernels responsibilty easing the problem of analysing the out put, > as opposed to making that the responsibilty of user space > postprocessing. Actually this is pushing the formatting out of the kernel, is more efficient, and it leaves more flexibility to the logging daemon! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/