








Your rating: Now say why...



| Downloads:4,304 |
| Version Downloads:3,853 |
| Type:Utilities : File Management |
| License:Shareware |
| Date:18 Mar 2006 |
| Platform:PPC / Intel |
| Price: $10.00 |
Overall (Version 1.x):![]() ![]() ![]() ![]() ![]() |
Features:![]() ![]() ![]() ![]() ![]() |
Ease of Use:![]() ![]() ![]() ![]() ![]() |
Value:![]() ![]() ![]() ![]() ![]() |
Stability:![]() ![]() ![]() ![]() ![]() |
+2
+2
If it is, $20 is a pretty ballsy ripoff for a simple gui to someone elses application. If it isn't, what can it do that fs_usage can't?
For the curious, your Mac comes with fs_usage. To try it out, here is a sample command:
sudo fs_usage -e -f filesys|grep -v CACHE_HIT|grep -v grep|grep -v mds
The -e prevents fs_usage from monitoring itself, the -f filesys make it monitor only filesystem activity (as opposed to network activity), the various grep -v foo parts tell fs_usage to ignore those various things (i.e. grep, mds, whatever else you don't want to monitor).
Why would you want to use it? If you have an app, say Safari, that is giving you the spinning pinwheel of death, fs_usage would be able to tell you what was going on when that lockup was happening. Might point to something you can fix (like a cache file that should be deleted). Of course, fs_usage has to already be running when this happens.
+448
egrep -v 'CACHE_HIT|grep|mds'
Or run something like:
sudo fs_usage -e Terminal mds
... to exclude Terminal and mds processes from the output. The -f option doesn't seem to have any effect and I'm not seeing any CACHE_HIT output on this system (eMac G4; 10.4.5).