Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Submission + - Nominum calls Open Source DNS 'a recipe for proble

Raindeer writes: "In an effort to promote its new Cloud based DNS service SKYE, Nominum one of the commercial DNS-software, providers slaundered all open source/freeware DNS packages. It said: "Given all the nasty things that have happened this year, freeware is a recipe for problems, and it's just going to get worse.(....) So, whether it's Eircom in Ireland or a Brazilian ISP that was attacked earlier this year, all of them were using some variant of freeware. Freeware is not akin to malware, but is opening up those customers to problems. " This has the DNS community fuming. Especially when you know Nominum was one of the companies affected by the DNS Cache poisoning problem of last year. Something PowerDNS, MaraDNS and DJBDNS all open source weren't vulnerable too."

Comment Re:Exists already in Linux kernel (Score 5, Informative) 212

I wrote OProfile, and I currently use DTrace daily, and I can assure you that you are wrong when you claim they do the same thing.

OProfile is useful for measuring system-wide resource consumers (for example, you can see what pieces of code are causing cache misses in the kernel when your apache process is in the kernel etc, or which user processes take up the most CPU time).

DTrace can also do something similar (though it needs a little more work yet). But DTrace does a LOT more than this. Imagine a system-wide (kernel, binaries, libraries) 'strace', where you can trivially choose what to print out, and what parts to strace, and under what circumstances. DTrace does even more than that.

OProfile can't tell you exactly why your system call is returning EINVAL. OProfile can't tell you why your application is causing cross-calls. OProfile can't tell you what processes are writing to what files, in real time. OProfile can't debug race conditions.

OProfile is a profiler: it does its job and nothing more. DTrace is, essentially, an instrumentation suite; one of its abilities is to function as a simple profiler.

You won't really get a notion of why DTrace is so useful until you try it.

Slashdot Top Deals

Quark! Quark! Beware the quantum duck!