linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: File change notification
Date: Wed, 31 Dec 2003 20:30:39 +0100	[thread overview]
Message-ID: <3FF323DF.5060708@web.de> (raw)
In-Reply-To: <18TJE-1qL-3@gated-at.bofh.it>

Rüdiger Klaehn wrote:
> Any help is appreciated. At the moment I am quite happy about what is 
> being logged, but I am not sure how to best expose this to the 
> interested user space processes. A device was the easiest way, and so 
> that is what I used. Other possibilities would be a file in /proc or 
> something completely different. I got the impression that dbus might be 
> useful for this, but I have no idea how to use it.

Maybe relayfs is suitable for this task: http://www.opersys.com/relayfs/

Regards,
René

       reply	other threads:[~2003-12-31 19:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18PG9-4og-27@gated-at.bofh.it>
     [not found] ` <18TgF-QJ-7@gated-at.bofh.it>
     [not found]   ` <18TJE-1qL-3@gated-at.bofh.it>
2003-12-31 19:30     ` René Scharfe [this message]
2004-02-07  8:29 File change notification John Ogness
2004-02-07 14:01 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2003-12-31 16:42 Rüdiger Klaehn
2003-12-31 18:20 ` Javier Fernandez-Ivern
2003-12-31 18:48   ` Rüdiger Klaehn
2004-01-01  1:28     ` Michael Clark
2004-01-01  1:58       ` Dave Jones
2004-01-01  2:18         ` Michael Clark
2004-01-01  2:30           ` Javier Fernandez-Ivern
2004-01-01 13:11       ` Rüdiger Klaehn
2003-12-31 20:49 ` Javier Fernandez-Ivern
2004-01-01  9:02 ` Juergen Hasch
2004-01-01 10:47 ` jw schultz
2004-01-01 12:44   ` Rüdiger Klaehn
2004-01-03  6:32     ` Jan Harkes
2002-11-01 21:31 file " Colin Burnett
2002-11-01 22:19 ` Chris Wright
2002-11-02 15:43   ` Jamie Lokier

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=3FF323DF.5060708@web.de \
    --to=l.s.r@web.de \
    --cc=linux-kernel@vger.kernel.org \
    /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).