2

This question already has an answer here:

In order to diagnose slow terminal interaction (which turned out to be an unrelated problem), I ran sudo opensnoop and saw output like this: dtrace errors

I assume this has to do with SIP in El Capitan. Is it something to worry about? How can I dig deeper to understand what the probe IDs correspond to and what processes are causing the errors? What is the action #?

marked as duplicate by bmike Dec 8 '15 at 16:51

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

2

You can white list portions of the restrictions when you boot to recovery HD and open terminal from the utilities window:

csrutil disable
csrutil enable --without dtrace

I haven't found good Apple documentation on this, but Rich Trouton has done a magnificent job documenting the internals of SIP on his blog and public speaking engagements:

Not the answer you're looking for? Browse other questions tagged .