Re: [gentoo-user] Nepomuk indexing, what triggers it?

[BRM]

----- Original Message ----

> From: Paul Hartman <paul.hartman+gentoo@×××××.com>
> To: gentoo-user@l.g.o
> Sent: Fri, November 19, 2010 11:31:39 AM
> Subject: Re: [gentoo-user] Nepomuk indexing, what triggers it?
>
> On Fri, Nov 19, 2010 at 9:17 AM, Alan McKinnon <alan.mckinnon@×××××.com>
>wrote:
> > Hi all,
> >
> > Haven't had much luck finding this  info:
> >
> > If I reboot this machine and start KDE, Nepomuk starts a  rather long-lived
> > index of my home directory. It takes up about 30-40%  cpu and lasts as much
>as
> > 15 minutes sometimes. This is annoying because  after a reboot I usually
want
> > to catch up on mail, rss feeds and fire up  VirtualBox. So nepomuk is just
> > wasting my time at this point.
>
> My  /guess/ is that it scans every time you restart to be sure nothing
> changed  while it was shutdown. It doesn't know if you've dual-booted,
> logged into  xfce, mounted the disk in another machine, had fsck remove
> files,  etc.
>
> I think Tracker behaves the same way in gnome-land.

To add to it - Nepomuk has two parts (according to 
http://nepomuk.kde.org/node/2) that seem to be active in here:
1. Strigi - 
http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/StrigiService
2. FileWatchService - 
http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/FileWatchService

From the FileWatchService info:

"However: due to the restrictions of all file watching systems  available 
(systems such as inotify are restricted to 8000 something  watches, fam does not 
support file moving monitoring, etc.) the service  mostly relies on KDirNotify. 
Thus, all operations performed by KDE  applications through KIO are monitored 
while all other operations (such  as console commands) are missed."

So it really does need to check up on things during restart to get back in sync, 
but also to find what it didn't know about from info not going through an 
interface it is aware of.

Ben