similar to: [DTrace] socketsnoop.d - TCP by PID

G''Day Folks, Well, this one was my white whale. I now have a demonstration program that uses Perl, Kstat, /proc/*/usage, /proc/*/psinfo, and DTrace. The program itself is more of a prototype, I want to get serious about it and rewrite it in C. It currently has output like, # prustat -t5 -snet 10 PID %CPU %Mem %Disk %Net COMM 90 0.00 0.09 0.00 0.00

Hi i''m trying to write my first dtrace script apparently i bit off a bit more than i can chew, i want to track io over sockets, i found your socketsize.d that gave me how to track writes, but i''m at a loss how to track reads, frankly i don''t see how your write tracker works because it uses a probe in a function that only takes two arguments but you grab size of write

G''Day Folks, I''ve just rewritten iosnoop so that uses command line arguments (I caved in and used a little Bourne shell for this - hence it''s lost it''s ".d" extension). It''s much more useful now. # iosnoop -h USAGE: iosnoop [-a|-A|-Degstv] [-d device] [-f filename] [-m mount_point] iosnoop # default output

Opening folders containing 10K files totaling 20GB is slow (takes 1.5 - 2.0 minutes) in FreeBSD 9.2 with Samba 4.1.11 on a system with 32GB RAM and a newer Xeon processor. Server is a standalone server that I'm using for testing. I am using nfsv4 acls. I used the procsystime dtrace script from here: http://www.brendangregg.com/DTrace/procsystime with the following syntax: procsystime -n smbd

G''Day Folks, I''ve finally typed up my classic DTrace demo, which I use to introduce people to DTrace (I delivered this at SOSUG#1), http://www.brendangregg.com/DTrace/dtracevstruss.html Here I create a fault and show the difficulty in analysing it using previous tools. Then I compare the impact of analysing the problem using both DTrace and truss. DTrace wins (a lot!).

Hi Here is System tap''s representives response to my comments and mine back to that list. Since it was on a public mailing list i''m reposting here, since there is obvious interest. James Dickens uadmin.blogspot.com ---------- Forwarded message ---------- From: James Dickens <jamesd.wi at gmail.com> Date: Sep 13, 2006 1:51 PM Subject: Re: Systemtap vs Dtrace web page

G''Day Folks, I''ve found another use of dtrace, this makes your console keyboard sound like a typewriter. http://www.brendangregg.com/DTrace/typewriter-0.70.tar.gz I''ve only tested it on an UltraSPARC 5 and a Pentium laptop so far, more to follow. Ok, sorry, not actually a practical use of DTrace. :) Enjoy! Brendan [Sydney, Australia]

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

If I use a simple dtrace script such as this: fbt::somefunc:entry{self->trace=1;} fbt::somefunc:return{self->trace=0;} fbt:::entry{} fbt:::return{printf("%lx", arg1);} then it will descend to whatever depth is necessary If I want to limit it to say 3 functions deep, how can I do that? The quick answer I want to use is to do "self->depth++" on each entry and then

Hi. I found this issue with IA64 box while looking at the c/s of 18204:21dd1fdb73d8, but I believe the things is same with x86 box. I''m not sure whether this patch coexist with the old ioemu which is to be removed soon. So it might be desirable to apply this patch after deleting the internal ioemu tree. thanks, xm: Don''t spawn vncviewer twice. Without this patch, vncviewer

i am doing reads and writes to /dev/rdsk/c0t2d0s4 using dtrace to see how much time it took for ssdread and ssdwrite. It shows very small number 4 or 5. #pragma D option flowindent syscall::pread:entry { self->trace = 1; self->size = arg2; } syscall::pwrite:entry { self->trace = 1; self->size = arg2; } fbt:ssd:ssdread:entry /self->trace/ { self->start = timestamp;

Hi Nils, all, I tried the ''FBT-trick'' suggested below by Nils and (of course :-) ) it works and gives me a pile of output. Good enough to show that indeed Linux application behavior is not totally opaque, good enough to for instance show that ''system call mapping'' is taking place. I wonder, is there any documentation available for lxsyscall module ? To learn

I have xkeybindings running just fine on centos 5. I have vncviewer running in full screen mode showing another PC. When vncviewer is running is running it seems to override my xkeybindings. Is there a way to tell vncviewer to not bind to any keys?? The only keys I am binding is on the Keypad 3,4,6, 9 and Enter. Nothing that vncviewer uses anyway. How can I still have my xkeybindings active

I have a host that I have been accessing with vncviewer via its fqdn that had only an IPv4 A record. I just added a AAAA IPv6 record, and vncviewer via fqdn stopped working. But worked when I provided the IPv4 address instead. It LOOKS like vncviewer is trying the IPv6 address, eventhough all documentation indicates that it does not support IPv6. Definitely my server is only listening on

I''ve attached the preliminary patch to add vncviewer options to the ''xl create''. It applies cleanly against c/s 4e1d091d10d8. All feedback is welcome. Goncalo # HG changeset patch # User Goncalo Gomes <goncalo.gomes@eu.citrix.com> # Date 1332257809 0 # Node ID 46f8afe643dee8de2c592c65204567fbad657616 # Parent 4e1d091d10d83130842170cd61f1194e5459f2aa Add

Hello, is there a way to start automatically the vncviewer when a domU starts? When I was using the xm toolstack I could use "xm create domain.cfg -vncviewer" or something similar (if I''m not wrong), but I don''t know how to do it with the xl toolstack. At the moment, I have to create the domain using xl create domU.cfg, then xl list to see the domU id and then xl

Hi, If you have a custom kernel (and therefore have duplicates of everything in /kernel in your custom kernel) and have noticed that when you try to use anonymous tracing, dtrace adds multiple copies of the forceload directives to /etc/system, e.g.: * vvvv Added by DTrace * * The following forceload directives were added by dtrace(1M) to allow for * tracing during boot. If these

I am looking for Dtrace scripts that can be used to collect data during performance tests. I am especially interested in IO but CPU, memory, threads, etc are needed as well. Thanks, Dave

Hi all, the patch "qemu-vnc-wmvi.patch" adds support for the WMVi pseudoencoding in qemu vnc server. If the client implements it, it is supposed to be able to change colour depth when receiving a WMVi message. Since I didn''t know any client that supports it and I wanted to test the implementation before submitting any patch I also modified vncviewer to support WMVi. The

I''m getting an odd behavior while trying to trace a mysql process using the -p flag on a Sun Cluster. This fails # dtrace -n ''pid$target::*mysql_parse*:entry {}'' -p `pgrep -x mysqld` dtrace: failed to grab pid 16537: process is traced Yet this works # dtrace -n ''pid$1::*mysql_parse*:entry {}'' `pgrep -x mysqld` dtrace: description