linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mo Re Ra <more7.rev@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: File monitor problem
Date: Wed, 4 Dec 2019 13:32:29 +0330	[thread overview]
Message-ID: <CADKPpc2RuncyN+ZONkwBqtW7iBb5ep_3yQN7PKe7ASn8DpNvBw@mail.gmail.com> (raw)

Hi,

I don`t know if this is the correct place to express my issue or not.
I have a big problem. For my project, a Directory Monitor, I`ve
researched about dnotify, inotify and fanotify.
dnotify is the worst choice.
inotify is a good choice but has a problem. It does not work
recursively. When you implement this feature by inotify, you would
miss immediately events after subdir creation.
fanotify is the last choice. It has a big change since Kernel 5.1. But
It does not meet my requirement.

I need to monitor a directory with CREATE, DELETE, MOVE_TO, MOVE_FROM
and CLOSE_WRITE events would be happened in its subdirectories.
Filename of the events happened on that (without any miss) is
mandatory for me.

I`ve searched and found a contribution from @amiril73 which
unfortunately has not been merged. Here is the link:
https://github.com/amir73il/fsnotify-utils/issues/1

I`d really appreciate it If you could resolve this issue.

Regards,
Mohammad Reza

             reply	other threads:[~2019-12-04 10:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 10:02 Mo Re Ra [this message]
2019-12-04 12:53 ` File monitor problem Amir Goldstein
2019-12-04 14:24   ` Mo Re Ra
2019-12-04 17:34     ` Jan Kara
2019-12-04 18:37       ` Amir Goldstein
2019-12-04 19:02         ` Matthew Wilcox
2019-12-04 20:27           ` Amir Goldstein
2019-12-11 10:06             ` Jan Kara
2019-12-11 13:58               ` Amir Goldstein
2019-12-16 15:00                 ` Amir Goldstein
2019-12-19  7:33                   ` Amir Goldstein
2019-12-23 18:19                     ` Jan Kara
2019-12-23 19:14                       ` Amir Goldstein
2019-12-24  3:49                         ` Amir Goldstein
2019-12-31 11:53                           ` Amir Goldstein
2020-01-07 17:10                           ` Jan Kara
2020-01-07 18:56                             ` Amir Goldstein
2020-01-08  9:04                               ` Jan Kara
2020-01-08 10:25                                 ` Amir Goldstein
2020-01-08 12:04                                   ` Jan Kara
2019-12-07 12:36       ` Mo Re Ra
2019-12-10 16:55         ` Jan Kara
2019-12-10 20:49           ` Amir Goldstein
2019-12-11 22:06             ` Wez Furlong
2019-12-12  5:56               ` Amir Goldstein

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=CADKPpc2RuncyN+ZONkwBqtW7iBb5ep_3yQN7PKe7ASn8DpNvBw@mail.gmail.com \
    --to=more7.rev@gmail.com \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).