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

Click here to return to the '10.5: Exploring OS X with dtrace' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Exploring OS X with dtrace
Authored by: ebrandwine on Oct 31, '07 02:03:08PM

Sorta. Not really. lsof is wonderful, but it prints a static dump of what's happening on the system right now. The dtrace example given above will print every file as it's opened. You can leave it running in a terminal, and spy on your system.

A much more complex example, one that's basically impossible with other tracing tools, is e.g. to print out details of all filesystem changes that happen within 100ms of a network connection being established. I've used this in production to figure out where a commercial product was stuffing connection data on disk.

(My day job is administering Solaris systems, FWIW)


[ Reply to This | # ]