From: Richard Weinberger <richard@nod.at>
To: Marian Marinov <mm@1h.com>,
"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 09:07:08 +0200 [thread overview]
Message-ID: <5382E81C.9070605@nod.at> (raw)
In-Reply-To: <538280EC.1010202@1h.com>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
Am 26.05.2014 01:46, schrieb Marian Marinov:
> 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.
Well, the patch itself has documented its major flaw:
+ * WARNING! This patch has been designed as EXPERIMENTAL. Its usage
+ * is DANGEROUS, because some filesystems could get exhausted by the
+ * masses of ORPHAN INODES!
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-05-26 7:07 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
2014-05-26 7:07 ` Richard Weinberger [this message]
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=5382E81C.9070605@nod.at \
--to=richard@nod.at \
--cc=jos.huisken@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=mm@1h.com \
--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