begin quoting Mike Marion as of Thu, Jul 24, 2008 at 11:27:41AM -0700: > Quoting "Todd Walton" <[EMAIL PROTECTED]>: > > >DTrace and the Linux bunker mentality > >http://blogs.zdnet.com/Murphy/?p=1198 > > Maybe it's just because I (admittedly) don't know dtrace that well > yet, but I find that I still get far more, and more helpful, info much > faster via strace, ltrace and the human readability of /proc on linux > then I do with dtrace on solaris or osx.
You have to stop your service and restart it to use strace. With DTrace, you can investigate *running* programs -- without stopping and restarting them (which often solves a certain class of problems, thus making the bug vanish all too often). > Sun keeps touting DTrace like the greatest thing since sliced bread > (and their ZFS) but it just doesn't seem to be all that much better to > me. Granted, compared to the info I tend to get from tools on solaris > (truss is almost identical to strace but /proc on solaris sucks IMNSHO > because it's not really human readable at all) DTrace is an improvement. I've seen DTrace used for debugging, monitoring, and optimizing. It is just that slick... you're not going to get too much profiling info from /proc, I imagine, and if you did, would you want to be slowing down all of your programs on the off chance you'd want to do this sort of thing? > BTW, you should see how many long time solaris admins just love how > easy info is to get from /proc in linux compared to solaris. The > links for exe/cwd and the fd path alone for processes is so much > nicer. No need to fire up lsof for something you can use ls for on > linux. Hm. Is this a feature of the new kernels? I have found the /linux proc to be better than the solaris /proc, but not by THAT much. -- I haven't had much need for DTrace either, as top generally suffices. Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
