On Sunday 26 July 2009 05:08:02 pm Anders Johansson wrote:
On Sunday 26 July 2009 23:04:19 David C. Rankin wrote:
and sure enough the beast was back.
Actually, forget what I said. It just occurred to me that nepomuk doesn't scan anything. That's strigi (which btw is disabled by default). nepomuk just lets you tag files manually, so you can search for the tags later. If it consumes 100% CPU, it's a bug and you need to report it
Anders
On the 4.3-0.1 release nepomuk went to 103% and just stuck there. That was *without* strigi indexer even being selected. I had to remove the autostart and kill nepomuservices to get my cpu back. As a test, I then set strigi to start and reenabled nepomuk autostart. Nepomuk behaved ok, small cpu load and then finished. Nothing like it was doing when strigi was not checked. Go figure... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org