[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvxx8_gJ+NAGVn_vZmkVfey45_1qTqAQnxKDCZD0gQsr5w@mail.gmail.com>
Date: Mon, 21 Apr 2014 00:22:32 +0200
From: Richard Weinberger <richard.weinberger@...il.com>
To: Michael Kerrisk <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?
On Fri, Apr 18, 2014 at 6:15 AM, Michael Kerrisk <mtk.manpages@...il.com> wrote:
> On Thu, Apr 17, 2014 at 11:28 PM, Lennart Sorensen
> <lsorense@...lub.uwaterloo.ca> wrote:
>> On Thu, Apr 17, 2014 at 11:00:37PM +0200, Jos Huisken wrote:
>>> I was trying to maintain a local and remote directory in sync with
>>> lsync, using inotify.
>>> I happen to have >4M files and >400k directories... running over
>>> /proc/sys/fs/inotify/max_user_watches
>>
>> Would fanotify perhaps be a better interface to use?
>
> (One of us is misunderstanding fanotify; it might be me.)
>
> Did you look at fanotify closely? I don't think it could be used for
> this task -- does not notify linka dn unlink events, difficult to set
> up recursive monitoring, etc.
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.
--
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