Re: [Tracker] the story on NFS
- From: Aleksander Morgado <aleksander lanedo com>
- To: "Brian J. Murrell" <brian interlinx bc ca>, "tracker-list gnome org" <tracker-list gnome org>
- Subject: Re: [Tracker] the story on NFS
- Date: Mon, 11 Nov 2013 11:08:11 +0100
On 11/11/13 03:20, Brian J. Murrell wrote:
I'm assuming that tracker uses [i|d]notify (either directly or
indirectly) to know when files need re-indexing (new or changed). Of
course [i|d]notify doesn't work on NFS.
So what's tracker's story when being pointed at an NFS mounted
directory? How does it know to re-index new and changed files?
As for watching files, does tracker use [i|d]notify directly or a
library for doing that?
Tracker uses GLib/GIO's GFileMonitor support to monitor files, which is
just a wrapper on top of several different monitoring systems, including
inotify, FAM, and others.
For the specific case of NFS mounts, GLib/GIO will try to use FAM if
available (since GLib 2.35.7 [1]), as FAM works over NFS. Otherwise it
will fallback to inotify, which won't work anyway. But note that this
will only be the case for $HOME NFS mounts [2].
[1]
https://mail.gnome.org/archives/ftp-release-list/2013-February/msg00056.html
[2] https://bugzilla.gnome.org/show_bug.cgi?id=592211
--
Aleksander
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]