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
On Fri, Nov 19, 2010 at 9:17 AM, Alan McKinnon alan.mckin...@gmail.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
- Original Message
From: Paul Hartman paul.hartman+gen...@gmail.com
To: gentoo-user@lists.gentoo.org
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.mckin...@gmail.com
Apparently, though unproven, at 18:31 on Friday 19 November 2010, Paul Hartman
did opine thusly:
On Fri, Nov 19, 2010 at 9:17 AM, Alan McKinnon alan.mckin...@gmail.com
wrote:
Hi all,
Haven't had much luck finding this info:
If I reboot this machine and start KDE, Nepomuk starts a
Apparently, though unproven, at 20:13 on Friday 19 November 2010, BRM did
opine thusly:
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
Alan McKinnon writes:
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
6 matches
Mail list logo
