From: Al Viro <viro@ZenIV.linux.org.uk>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Jamie Lokier <jamie@shareable.org>,
Sylvain Rochet <gradator@gradator.net>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: PROBLEM: 2.6.35.7 to 3.0 Inotify events missing
Date: Sat, 20 Aug 2011 03:01:47 +0100 [thread overview]
Message-ID: <20110820020147.GE2203@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20110819184311.b094d6b7.rdunlap@xenotime.net>
On Fri, Aug 19, 2011 at 06:43:11PM -0700, Randy Dunlap wrote:
> What do you suggest as a functioning alternative to inotify?
Depends on what particular (ab)use do you have in mind...
next prev parent reply other threads:[~2011-08-20 2:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101018223540.GA20730@gradator.net>
2011-08-19 23:03 ` PROBLEM: 2.6.35.7 to 3.0 Inotify events missing Sylvain Rochet
[not found] ` <20110819230344.GA24784-XWGZPxRNpGHk1uMJSBkQmQ@public.gmane.org>
2011-08-19 23:37 ` Jamie Lokier
[not found] ` <20110819233756.GI11512-DqlFc3psUjeg7Qil/0GVWOc42C6kRsbE@public.gmane.org>
2011-08-20 0:47 ` Sylvain Rochet
2011-08-20 3:21 ` Jamie Lokier
2011-08-20 1:29 ` Al Viro
2011-08-20 1:43 ` Randy Dunlap
2011-08-20 2:01 ` Al Viro [this message]
[not found] ` <20110820012943.GD2203-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2011-08-20 3:03 ` Jamie Lokier
[not found] ` <20110820030335.GA14899-DqlFc3psUjeg7Qil/0GVWOc42C6kRsbE@public.gmane.org>
2011-08-21 17:07 ` J. Bruce Fields
[not found] ` <20110821170714.GB9296-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-08-21 20:20 ` Jamie Lokier
2011-08-21 23:07 ` NeilBrown
2011-08-22 17:22 ` J. Bruce Fields
[not found] ` <20110822172239.GA15960-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-08-22 23:21 ` NeilBrown
2011-08-25 21:47 ` Sylvain Rochet
2011-08-21 22:29 ` NeilBrown
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=20110820020147.GE2203@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=gradator@gradator.net \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).