On Sat, 2012-06-23 at 01:55 +0200, Kernel Guardian wrote: > On every boot on of the trackers tracker-miner-fs or tracker-store eat > from 30-80% of cpu depends of cpu architecture. It takes minute or > two, then everything become normal. Just throwing a thought out: On ye olde Fedora, it would run a makewhatis run once a day, usually scheduled in the wee hours of the morning, where it shouldn't be a problem to users. For systems running continuously, that made sense, and worked well. But for systems that are only booted up from time to time, and not left running 24/7. You had one of two problems: The morning run never run. Or, the scan could be done once a day whenever you did have the computer running, and some computers did get bogged down during its scan. Has this tracker taken the second approach? And would trying the "morning scan" approach sidestep the issue? -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
