From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 24 Sep 2002 17:23:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 24 Sep 2002 17:23:39 -0400 Received: from pincoya.inf.utfsm.cl ([200.1.19.3]:11273 "EHLO pincoya.inf.utfsm.cl") by vger.kernel.org with ESMTP id ; Tue, 24 Sep 2002 17:23:38 -0400 Message-Id: <200209242127.g8OLRTxN005667@pincoya.inf.utfsm.cl> To: Larry Kessler cc: Jeff Garzik , Chris Friesen , Rusty Russell , linux-kernel mailing list , Alan Cox , cgl_discussion mailing list , evlog mailing list , Hien Nguyen , James Keniston , Mike Sullivan Subject: Re: [evlog-dev] Re: alternate event logging proposal In-Reply-To: Message from Larry Kessler of "Tue, 24 Sep 2002 14:11:31 MST." <3D90D503.8F4CDEB6@us.ibm.com> Date: Tue, 24 Sep 2002 17:27:29 -0400 From: Horst von Brand Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Larry Kessler said: [...] > Event logging uses real-time signaling to notify a process that's registered > for notification that an event matching the criteria defined during > registration has been written to the event log. When notified, the process > can read the entire event from the event log and then do whatever. How is said event found? By scanning the whole log? -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513