From: Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk>
To: "Tiberiu C. Turbureanu" <tct@ceata.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Maximum number of inotify watches
Date: Wed, 22 Jun 2011 15:28:35 +0100 [thread overview]
Message-ID: <201106221528.35648.tvrtko.ursulin@onelan.co.uk> (raw)
In-Reply-To: <bbaaf72bb3386008c77db2e16112b330@ceata.org>
On Wednesday 22 Jun 2011 13:59:20 Tiberiu C. Turbureanu wrote:
> Hello,
>
> I want to monitor all the files on a server using one instance of
> inotify and about 20M watches recursively set on directories in '/' tree
> substructure. I'd want to be notified about all type of events defined
> by inotify (create, delete, access, modify etc.)
>
> Assuming this monitor daemon running in user-space keeps up with the
> frequency of new events in the kernel queue (it reads them), is it
> possible to exceed the kernel memory limit because there are too many
> watches and events?
It does sounds unrealistic with your number of watches.
Have a look at fanotify which will give you a subset of inotify events for
just one watch per mount point. If you really need events which are not
available maybe they can be added.
Tvrtko
prev parent reply other threads:[~2011-06-22 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 12:59 Tiberiu C. Turbureanu
2011-06-22 14:28 ` Tvrtko Ursulin [this message]
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=201106221528.35648.tvrtko.ursulin@onelan.co.uk \
--to=tvrtko.ursulin@onelan.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tct@ceata.org \
/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
all inboxes | Powered by JetHome®