similar to: User defined tick-n probe.

Hello, I''m building some simple monitoring tools to watch zfs storage servers. Is this possible to run dtrace script for example 10 seconds? (Of course it is, I just trying to figure out how). Right know it has to be stopped by "CTRL-C" I''m particulary interested in scripts like iscsiio.d, iscsiwho.d from

Just showing someone how great DTrace is and then we spot something I do not understand. Of course it can be a major misunderstanding of myself. Would appreciate another (expert) look upon this. The goal we try to achieve is trying to get insight if there is a bursty nature in the time slot when system calls are done. Following DTrace snippet is tried: dtrace -q -p 3173 -n

DTraceToolkit has a dtrace script (Proc/pidpersec.d) that refers to a variable mpid as below profile:::tick-1sec { printf("%-22Y %8d %6d\n", walltimestamp, `mpid, pids); pids = 0; } Where is `mpid getting picked from (it isn''t declared anywhere else)? What does the character ` in `mpid signify? I do not see any reference to this variable in the dtrace

We are using following dtrace script to analyze an application. However we see different number of lwp_yield and yield calls reported depending on whether we trace mutex_lock or mutex_unlock or not. The number reported when we are not tracing mutex_lock or mutex_unlock is higher. What could be going on here and which one is the correct number. This is on S10 U2. Thanks, Rao.

HI, T5220, S10U4 + patches mdb -k > ::memstat While above is working (takes some time, ideally ::memstat -n 4 to use 4 threads could be useful) mpstat 1 shows: CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl 48 0 0 1922112 9 0 0 8 0 0 0 15254 6 94 0 0 So about 2mln xcalls per second. Let''s check with dtrace:

Hi, I wish to create a series of plots with the same x-axis range and the same placement of tick marks. In addition I want to force the tick marks to be at specific locations. For example, if I wish to have an x-axis which goes from 40 to 110, with tick marks at 40, 50, 60, ... , How can I accomplish that? The various parameters I have tried changing just seem to be suggestions for

Hi. T2000 1.2GHz 8-core, 32GB RAM, S10U3, zil_disable=1. Command ''zpool export f3-2'' is hung for 30 minutes now and still is going. Nothing else is running on the server. I can see one CPU being 100% in SYS like: bash-3.00# mpstat 1 [...] CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl 0 0 0 67 220 110 20 0 0 0 0

why do I need to use Control-c to stop my trace, for example: #dtrace -n ''profile:::tick-1sec/++x == 10/ {exit(0)}'' in my system with heavy IO load, I have to use Control-c without heavy IO, the same trace cmd just return automatically after 10 sec. I just assume Control-c is to deliver a signal to dtrace, but why do I have to in some cases (like I have a heavy IO load)?

Hello, I use Brendan''s sysperfstat script to see the overall system performance and found the the disk utilization is over 100: 15:51:38 14.52 15.01 200.00 24.42 0.00 0.00 83.53 0.00 15:51:42 11.37 15.01 200.00 25.48 0.00 0.00 88.43 0.00 ------ Utilisation ------ ------ Saturation ------ Time %CPU %Mem %Disk %Net CPU Mem

I''m looking for an example of how one could write a dtrace probe that could follow something like a NULL terminated linked list. For example: struct list { struct list *next; void *data; }; struct list *list_root; Assuming I had "list_root" available, but I wanted to know how long the linked list is, how can I do this in a dtrace probe? If I had looping

i''m running the following script: #pragma D option quiet profile:::tick-1sec / ++x >= 15 / { exit(0); } io:::start { @io_size[execname] = sum(args[0]->b_bcount); } on exit, the script prints out the value of @io_size, why? there''s no printa(), and i also specified "D option quiet" (i also tried -q). this seems to happen with any kind of probe: on exit(0) all

[Perhaps someone could rename this list to dtrace-matt-problems-discuss?] If I run this script against my binary (which contains a USDT probe called ''concurrentq-latency''): ::: / probename == "concurrentq-latency" / { printf("[%s]:[%s]:[%s]\n", probeprov, probefunc, probename); } I get this output: dtrace: script ''testq.d'' matched 46056

I recently did a backport of a couple of networking bug fixes from s10x_u4_b6 to s10x_u3_b10. I patched just /platform/i86pc/kernel/unix and /platform/i86pc/kernel/amd64/unix in my existing u3 OS image and I''m seeing this dtrace problem when running any dtrace script: NODE hcb101 ~ $ ./tcpstat.sh dtrace: failed to compile script /dev/fd/10: "/usr/lib/dtrace/procfs.d", line

Hi all, I have questions about something I observed just now: 1) on AMD64, S10u1: # dtrace -n ''fbt::copystr:entry{printf ("%p\n", args[0]);}'' -c /bin/pwd dtrace: invalid probe specifier fbt::copystr:entry{printf ("%p\n", args[0]);}: in action list: index 0 is out of range for fbt::copystr:entry args[ ] but # dtrace -n ''fbt::copystr:entry{printf

Hello, Is there a way to define the width of the axis tick marks on traditionnal plots? I did not find anything specific on this topic in the help and par(lwd=...) does not affect the tick marks. I guess that using axes=FALSE and recreating the axis with the axis() command could do the trick but I wonder if there is no easier way. Thanks in advance Sebastien

Hi, I am adding DTrace probes within NFS v3 client. In my current implementation, I use some tsd_*() functions and kmem_zalloc() function. These functions might be heavy and affect the performance. I want to call this function only when DTrace is running or the DTrace probes are enable. So is there a way to check DTrace is running or DTrace probe is enabled? Regards, Danhua

Hi Folks, I''m trying to use DTrace to understand some complex code using the user process probe. Things are basically not matching up. When I use a variable to track depth, sometimes it jumps. Similarly, the flow indent seems off. I read another post saying that this is caused by missing return statements in functions.

>From time to time a jboss process would end eating all, the available CPU and the load avg would skyrocket. Once the operators restarted jboss, the system''d be normal again (sometimes for weeks) until the next incident Since we moved the app from a v440 running Solaris 10 8/07 to a t2000 running Solaris 10 5/08 the problem started to happen more frequently (2-3 times a week). The

Hi, Here is my situation : I have installed Samba 2.0.6 on my computer, which is running with Linux RedHat 6.0. When somebody tries to connect to this server, he's got a 'refused connection' message after he tried to my_IP@:139. I don't think the smb.conf is responsible because we have tried with the basic one, and it doesn't change anything. As I'm fresh in Linux (and