That was a weird typo. Appreciate the catch.
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
# dtrace -qn 'syscall:::exec-success { trace (execname); }'
^
The exec-success probe is managed by the proc provider, not
the syscall provider. So the probe designation should be;
proc:::exec-success (or just 'exec-success').
(for t
Michael, James, Richard!
Thanks a lot for all your suggestions! It helped a lot, I have blogged
it here http://blogs.sun.com/amitsaha/entry/introducing_dtrace_to_newbies
Thanks!
-Amit
On Sat, Mar 21, 2009 at 1:13 AM, Michael Ernest
wrote:
> One aspect of DTrace I enjoy is that you can show pe
One aspect of DTrace I enjoy is that you can show people something surprising
without a lot of foundational knowledge.
You can ask a question like this: If you wanted to know how many processes were
running on your system at any time, how would you do it? Most people even
lightly familiar with
I like Bryan Cantrill's Google video, a bit long for your audience but still
he has a way of drawing in the audience, but I am a Sys-Admin who gets into
this stuff.
James Dickens
Uadmin.blogspot.com
On Fri, Mar 20, 2009 at 3:23 AM, Amit Saha wrote:
> Hi all,
>
> Here is how I would like to int
Hi all,
Here is how I would like to introduce DTrace to an audience which is
not aware of anything remotely related to observability of a system.
Please feel free to provide your suggestions, because that is the only
way this will help me in my effort. Thank You.
To introduce DTrace, you will
