From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: move udev-rules parsing into the daemon
Date: Sat, 06 Aug 2005 03:41:06 +0000 [thread overview]
Message-ID: <20050806034106.GA27986@vrfy.org> (raw)
In-Reply-To: <20050731004227.GA26803@vrfy.org>
On Fri, Aug 05, 2005 at 05:39:52PM -0700, Greg KH wrote:
> On Tue, Aug 02, 2005 at 04:42:44AM +0200, Kay Sievers wrote:
> > +static int watch_directory(const char *dir)
> > +{
> > + int fd;
> > +
> > + fd = open(dir, O_RDONLY);
> > + if (fd < 0) {
> > + err("could not open '%s' to watch it", dir);
> > + return -1;
> > + }
> > + if (fcntl(fd, F_NOTIFY, DN_MODIFY | DN_CREATE | DN_DELETE | DN_MULTISHOT) = -1) {
> > + err("could not set dnotify on '%s'", dir);
> > + return -1;
> > + close(fd);
> > + }
> > +
> > + return 0;
> > +}
>
> Why dnotify and not inotify?
The patch is just older than inotify is in mainline. :)
If we can require the latest kernel, I will happily change it.
Thanks,
Kay
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-08-06 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 0:42 move udev-rules parsing into the daemon Kay Sievers
2005-08-02 2:42 ` Kay Sievers
2005-08-06 0:39 ` Greg KH
2005-08-06 3:41 ` Kay Sievers [this message]
2005-08-09 2:30 ` Kay Sievers
2005-08-11 6:13 ` Greg KH
2005-08-11 23:06 ` Kay Sievers
2005-08-12 2:49 ` Kay Sievers
2005-08-12 18:04 ` Greg KH
2005-08-18 19:23 ` Kay Sievers
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=20050806034106.GA27986@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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).