From: Marian Marinov <mm@1h.com>
To: Richard Weinberger <richard@nod.at>,
"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, 26 May 2014 02:46:52 +0300 [thread overview]
Message-ID: <538280EC.1010202@1h.com> (raw)
In-Reply-To: <538091C2.6040802@nod.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/24/2014 03:34 PM, Richard Weinberger wrote:
> Am 24.05.2014 09:52, 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.
>>> Currently I'm using a fuse overlay filesystem to log everything. Not perfect but works... :-)
>>
>> Richard,
>>
>> A late follow up question. How does your application deal with the event overflow problem (i.e., when you get a
>> large number of events much faster than your application can deal with them?
>
> The downside of the FUSE approach is that you have to intercept every filesystem function. This can be a
> performance issue. But due to this design the overflow problem cannot happen as the FUSE filesystem blocks until
> the event has been proceed.
>
Have anyone of you looked at this: https://github.com/1and1/linux-filemon/
I haven't stress tested it, but in the past I ported it to more recent kernels:
https://github.com/hackman/filemon-patches
It is not polished, but it works.
I'm considering fixing some of the issues at has for use in my home setup.
Marian
> Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a
> message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read
> the FAQ at http://www.tux.org/lkml/
>
- --
Marian Marinov
Founder & CEO of 1H Ltd.
Jabber/GTalk: hackman@jabber.org
ICQ: 7556201
Mobile: +359 886 660 270
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlOCgOwACgkQ4mt9JeIbjJSXrgCdHCFADxvKN3Hxb4qinc/5Fj6V
WYMAnArk3Zb8YqTUNoyNCh1zYplUUx9B
=y/Sm
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-05-25 23:46 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
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 [this message]
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=538280EC.1010202@1h.com \
--to=mm@1h.com \
--cc=jos.huisken@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=mtk.manpages@gmail.com \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.