linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Kessler <kessler@us.ibm.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	cgl_discussion mailing list <cgl_discussion@osdl.org>,
	evlog mailing list <evlog-developers@lists.sourceforge.net>,
	Hien Nguyen <hien@us.ibm.com>,
	James Keniston <kenistoj@us.ibm.com>,
	Mike Sullivan <sullivam@us.ibm.com>
Subject: Re: [evlog-dev] Re: alternate event logging proposal
Date: Tue, 24 Sep 2002 14:11:31 -0700	[thread overview]
Message-ID: <3D90D503.8F4CDEB6@us.ibm.com> (raw)
In-Reply-To: 3D90CC8F.4080706@pobox.com

Jeff Garzik wrote:
> 
> Larry Kessler wrote:
> > Jeff Garzik wrote:
> >>To address your more general point, a general way to notify interested,
> >>credentialed (is that a word?) 3rd party processes of device events
> >>would indeed be useful.  Since such events are essential out-of-band
> >>info, netlink might indeed be applicable.
> >
> >
> > Event Logging has both a command and an API for apps in user-space to
> > register for specific events (kernel or userspace).   The user must have
> > read access to the log file and the proper credentials in the allow/deny
> > file scheme (that's modeled after crontab).
> 
> Ok.  And?  It sounds like event logging could possibly use netlink as
> the event delivery mechanism.

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.
.
It's intended to satisfys the requirement for a "general way to notify...processes".
To read more, go to...
http://evlog.sourceforge.net/posix_evlog.html#_Toc525541312

  reply	other threads:[~2002-09-24 21:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24  1:54 [PATCH-RFC} 3 of 4 - New problem logging macros, plus template generation Larry Kessler
2002-09-24  2:12 ` Jeff Garzik
2002-09-24  5:47   ` Rusty Russell
2002-09-24  6:05     ` Jeff Garzik
2002-09-24  7:06       ` Rusty Russell
2002-09-24  7:23         ` Jeff Garzik
2002-09-24  7:30           ` Rusty Russell
2002-09-24 19:48             ` alternate event logging proposal Jeff Garzik
2002-09-24 19:57               ` Chris Friesen
2002-09-24 20:03                 ` Jeff Garzik
2002-09-24 20:54                   ` Tim Hockin
2002-09-24 22:32                     ` Brad Hards
2002-09-24 23:31                       ` Jeff Garzik
2002-09-24 23:37                         ` Brad Hards
2002-09-24 23:59                           ` Tim Hockin
2002-09-24 23:38                         ` Tim Hockin
2002-09-25  0:09                           ` Ben Greear
2002-09-25  0:47                             ` Tim Hockin
2002-09-25  1:14                               ` Brad Hards
2002-09-25  1:38                                 ` Tim Hockin
2002-09-24 20:09                 ` Jeff Garzik
2002-09-24 20:27                   ` [evlog-dev] " Larry Kessler
2002-09-24 20:35                     ` Jeff Garzik
2002-09-24 21:11                       ` Larry Kessler [this message]
2002-09-24 21:26                         ` Jeff Garzik
2002-09-25  0:15                           ` Larry Kessler
2002-09-24 21:27                         ` Horst von Brand
2002-09-24 21:50                           ` Larry Kessler
2002-09-25 14:44                 ` Lars Marowsky-Bree
2002-09-24 20:54               ` [evlog-dev] " Daniel E. F. Stekloff
2002-09-24 21:04                 ` Jeff Garzik
2002-09-30 22:43                 ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D90D503.8F4CDEB6@us.ibm.com \
    --to=kessler@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cfriesen@nortelnetworks.com \
    --cc=cgl_discussion@osdl.org \
    --cc=evlog-developers@lists.sourceforge.net \
    --cc=hien@us.ibm.com \
    --cc=jgarzik@pobox.com \
    --cc=kenistoj@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sullivam@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).