Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the '10.4: A way to check on a Spotlight indexing problem' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: A way to check on a Spotlight indexing problem
Authored by: bozoface on Sep 13, '05 12:32:21AM

Lsof is really useful, did not know about it previously.

I had "mds" running seemingly continuously (had been running for half a day
at least), "top" showed it usually using 50% cpu, though mdimport was
usually not listed in the "top".

I tried this hint and found that the only file of mine
that mdimport had open was a .DS_Store file. Checked back 10 minutes later
and *the same* .DS_Store file is still the only open file of mine
(a bunch of library files that mdimport uses were open of course).

Is this (indexing a .DS_Store for minutes or hours) normal?

I deleted that .DS_Store, did a kill -HUP on mds, and a few minutes later it got stuck on a different .DS_Store file.

I deleted that one too, and now mds is no longer in the top, and
lsof | | grep mdimport no longer shows it hanging(?) on a .DS_Store.
Back to normal, evidently.

But I fear for what Spotlight must be doing to "regular" non-power users
out there...

I deleted that one

[ Reply to This | # ]