Messages in this thread | | | Date | Tue, 22 Apr 2014 21:59:05 +0200 | Subject | Re: inotify, new idea? | From | Jos Huisken <> |
| |
Seems like also 'mv' events are also not supported by fanotify, like creation/deletion. Therefore not an option (for lsyncd) probably. Maybe loggedfs is (if time permits...). Thanks for the discussion.
Jos
On Mon, Apr 21, 2014 at 5:01 PM, Richard Weinberger <richard@nod.at> wrote: > > > Am 21.04.2014 15:31, 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. >> >> Then, we're understand the same thing: you're out of luck :-}. >> >>> Currently I'm using a fuse overlay filesystem to log everything. >>> Not perfect but works... :-) >> >> Interesting notion. I need to get to grips with FUSE... > > e.g. http://loggedfs.sourceforge.net/ > > Thanks, > //richard
| |