similar to: DT race

Good Morning, I would like to run a question by your technical support team. My employer is currently using Samba server (Samba 2.0.5a) Solaris 8 sun4u sparc SUNW,Ultra-4. Samba is configured to communicate through port 139. However we have been asked to change Samba configuration in order to change the communication from port 139 to 445. This configuration change is requested to improve

I''m using a fbt probe where I get a system call id as an argument, how do I look up the name of it? At the moment I''m post-processing the output using /etc/name/to_sysnum but that doesn''t feel right :) cheers, /Martin -- This message posted from opensolaris.org

How can I tell if this is normal behaviour? Oracle imports are horribly slow, an order of magnitude slower than on the same hardware with a slower disk array and Solaris 9. What I can look for to see where the problem lies? The server is 99% idle right now, with one database running. Each sample is about 5 seconds. I''ve tried setting kernel parameters despite the docs saying that

Dtrace does work on some workstation, such as as follows, ----------------------------------------------------------- bash-3.00# dtrace -s ./mem.d `pgrep test` dtrace: script ''./mem.d'' matched 5 probes ^C bash-3.00# uname -a SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100 bash-3.00# dtrace -V dtrace: Sun D 1.1

All, With Jon Haslam''s exciting news about the DTrace doc wiki (if you haven''t seen it yet, make your way to http://wikis.sun.com/display/DTrace), and with some of the discussion with the Apple folks, I''m wondering if the time isn''t right for something of a DTrace summit, perhaps as an unconference. The idea here would not be a DTrace user group (though that

Hi Max/DTrace list, > At any rate, without the -C, I can''t use #include <sys/stream.h>. > Without the #include <sys/stream.h>, I can''t use the M_DATA. > As it is, I get the following: > > # ./strrput.d 0xd595a6c0 <-- this is a vnode for a socket > ftp is using (not important here) > dtrace: failed to compile script ./strrput.d: line 7: >

Hi Expert I want to use dtrace to monitor the content change of one file. I made following scripts, #!/usr/sbin/dtrace -s inline int MYPID = $1; syscall::write:entry /pid == MYPID/ { tracemem(arg1, arg2); printf("\n"); } It always has an following error bash-3.00$ sudo dumpFIFO.dtrace 3836 dtrace: failed to compile script ./dumpFIFO.dtrace: line 19: tracemem( ) argument #2

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

Hi All, One of the customer is seeing the following error messages. He is using a S10U1 system with all latest patches. Dtrace script is attached. I am not seeing these error messages on S10U2 system. What could be the problem? Thanks, Gangadhar. ------------------------------------------------------------------------ rroberto at njengsunu60-2:~$ dtrace -AFs /lib/svc/share/kcfd.d dtrace:

DTrace folks, I''m pleased to introduce a potential new DTrace-sponsored project: the Erlang DTrace provider. To be good OpenSolaris citizens, we want to put the formation of this officially sponsored project to a vote -- as outlined in the OpenSolaris Constitution -- so here are the details for the new Project, as prepared by the Project Team: Name : Erlang DTrace Integration

Just adding a few more details to the previous mail so that I can avoid some trouble for you folks. 1. I have done a /execname != "dtrace"/ to avoid dtrace itself causing more syscalls to be fired. 2. I have also supressed the printing on the terminal which makes dtrace slower. And what happens is this: dtrace -qn ''syscall::read:entry /execname != "dtrace"/ {

X.Org has adopted GNU autoconf as its build configuration mechanism, so when I integrated the dtrace probes, I checked to see if they should be built using this test, checking for the existence of a program named "dtrace" in the path: dnl Check for dtrace program (needed to build Xserver dtrace probes) AC_ARG_WITH(dtrace, AS_HELP_STRING([--with-dtrace=PATH], [Enable dtrace

I have inserted some probes in my application, and it works great in the "debug build" I have been using. So I wanted to look at the "overhead" introduced by inactive dtrace probes in my application. I am using the Sun Studio 11 compiler, so I added the following options: -xO5 -g0 -xbuiltin But this breaks the linking of my application. Undefined first

Dear dtrace Experts, I have seen some dtrace utilities like opensnoop and execsnoop etc. My interest is to write a simple script that can snoop the files which uses the 3 syscalls like open,create,unlink. I have gone through dtrace oneliners that can do the same : dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0));}'' dtrace -n

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

Hey, Do you guys think that is a good idea to have a manual page for each provider with a complete description of what probes are offered ? Found some already under 7D category: dtrace dtrace (7d) - DTrace dynamic tracing facility fasttrap fasttrap (7d) - DTrace user instruction tracing provider fbt fbt (7d) - DTrace function boundary tracing provider

I am teaching a DTrace class and a student noticed that 2 iosnoop scripts run in two different windows were producing different results. I was not able to answer why this is. Can anyone explain this. Here are the reults from the two windows: # io.d ... sched 0 <none> 1024 dad1 W 0.156 bash 1998

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, As I''ve discussed before whenever we add USDT probes to a C++ function and call dtrace -l we get the mangled C++ name for the dtrace function, being listed :( Now the point of USDT probes is to abstract a higher level semantic construct for users to make use of. Surely it is not meant to be listing Unstable Interfaces (implementation details), such as the containing C++

> Your best bet to getting a supported (and *working*) > configuration with updated dtrace would be to upgrade > the OS. Solaris 10 update 5 is latest I reckon and > update 6 would be out real soon now. Full Ack. It''s quite difficult, though, to predict what DTrace features one will get when installing Solaris 10 (whatever release). There is nothing about the fine details of