[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <535532B3.6060800@nod.at>
Date: Mon, 21 Apr 2014 17:01:07 +0200
From: Richard Weinberger <richard@....at>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
CC: Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
Jos Huisken <jos.huisken@...il.com>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: inotify, new idea?
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists