> Nah. I just thought, that this should be accessible to unprivileged user. Or > if not, then the error message should state that, not that there are no > probes matching :::entry...
The reason that no probes are available to unprivileged users is that even trivial uses of DTrace can consume extensive system resources such as memory. Initially, we wanted to take the conservative approach of disabling DTrace for all but the root user by default. Now that we've built up some experience with DTrace, it may be time to consider adding dtrace_proc to the default privilege set, and making sure we have the necessary resource controls. Adam -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
