linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Jos Huisken <jos.huisken@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: inotify, new idea?
Date: Mon, 21 Apr 2014 17:01:07 +0200	[thread overview]
Message-ID: <535532B3.6060800@nod.at> (raw)
In-Reply-To: <53551DB0.6030302@gmail.com>



Am 21.04.2014 15:31, schrieb Michael Kerrisk (man-pages):
> On 04/21/2014 10:42 AM, Richard Weinberger wrote:
>> Am 21.04.2014 09:24, schrieb Michael Kerrisk:
>>>> Does recursive monitoring even work with inotify?
>>>> Last time I've tried it did failed as soon I did a mkdir -p a/b/c/d because
>>>> mkdir() raced against the thread which installes the new watches.
>>>
>>> As I understand it, you have to program to deal with the races (rescan
>>> directories after adding watches). I recently did a lot of work
>>> updating the inotify(7) man page to discuss all the issues that I know
>>> of, and their remedies. If I missed anything, I'd appreciate a note on
>>> it, so that it can be added. See
>>> http://man7.org/linux/man-pages/man7/inotify.7.html#NOTES
>>
>> I'm aware of the rescan hack, but in my case it does not help
>> because my program must not miss any event.
> 
> Then, we're understand the same thing: you're out of luck :-}.
> 
>> Currently I'm using a fuse overlay filesystem to log everything.
>> Not perfect but works... :-)
> 
> Interesting notion. I need to get to grips with FUSE...

e.g. http://loggedfs.sourceforge.net/

Thanks,
//richard

  reply	other threads:[~2014-04-21 15:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 21:00 inotify, new idea? Jos Huisken
2014-04-17 21:28 ` Lennart Sorensen
2014-04-18  4:15   ` Michael Kerrisk
2014-04-20 17:44     ` Lennart Sorensen
2014-04-20 22:22     ` Richard Weinberger
2014-04-21  7:24       ` Michael Kerrisk
2014-04-21  8:42         ` Richard Weinberger
2014-04-21 13:31           ` Michael Kerrisk (man-pages)
2014-04-21 15:01             ` Richard Weinberger [this message]
2014-04-22 19:59               ` Jos Huisken
2014-05-24  7:52           ` Michael Kerrisk (man-pages)
2014-05-24 12:34             ` Richard Weinberger
2014-05-25 23:46               ` Marian Marinov
2014-05-26  7:07                 ` Richard Weinberger
2014-05-26  6:06               ` Michael Kerrisk (man-pages)

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=535532B3.6060800@nod.at \
    --to=richard@nod.at \
    --cc=jos.huisken@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=mtk.manpages@gmail.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).