(Google told me that there was an error, so I'm resending. Sorry if this is a duplicate)
On Sat, Jul 30, 2011 at 9:55 PM, Michael_google gmail_Gersten <[email protected]> wrote: >> the mds process dies with a variety of ugly errors, access violation, assert >> errors and >> a variety of other excuses… >> >> >> Apple support seemed to think that the problem was caused by some corrupt >> files but >> gave no hints on how to find the rascals ( the crash dumps generally did not >> provide >> this piece of info). > > I recall seeing some sort of information about a file activity tracing > program, that actually traced kernel calls made by a process. > > If you can find such a utility, and then ask it to monitor the kernel > file IO calls (or even just "open") for mdworker, that will probably > tell you which files it finally dies on. Alright, the "raw" command line program is "dtrace", but presumably there's better (nicer) front-ends to that. _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
