Comment 5 for bug 602211

Revision history for this message
Seif Lotfy (seif) wrote : Re: [Bug 602211] Re: Monitoring for new files

If we go with Tracker then:
1) we will need to use their uuid stuff
2) new dependancy?

On Mon, Jul 19, 2010 at 10:24 AM, Mikkel Kamstrup Erlandsen
<email address hidden> wrote:
> Inotify still sucks rest assured :-)
>
> A watch on a dir will only tell us when some unspecified thing happens
> to some unspecified file in that directory. We could install monitors
> directly on the last N (fx. 100) actual file inodes perhaps, but I am
> reluctant to do that - what happens when we aren't running? Do you wanna
> stat() all the last N files on startup (eeeeek!)?
>
> In any case this could be done entirely in an extension.
>
> As I said before I think FANotify and/or btrfs is our only hope here -
> or actually using Tracker directly to monitor these events. Tracker is
> probably the most advanced file monitor out there these days.
>
> --
> Monitoring for new files
> https://bugs.launchpad.net/bugs/602211
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Zeitgeist Framework: New
>
> Bug description:
> I  was thinking on how tracker monitors new files to index. Turns out they monitor directories using inotify. Recurse XDG dirs and single iterate $HOME
> Does this make sense to us?
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/zeitgeist/+bug/602211/+subscribe
>

--
This is me doing some advertisement for my blog http://seilo.geekyogre.com