diff options
Diffstat (limited to 'cddl/contrib/dtracetoolkit/Man')
231 files changed, 13703 insertions, 0 deletions
diff --git a/cddl/contrib/dtracetoolkit/Man/Readme b/cddl/contrib/dtracetoolkit/Man/Readme new file mode 100644 index 000000000000..31641230863b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/Readme @@ -0,0 +1,40 @@ +Man - Man pages + + There are a number of ways you can read these man pages. Either, + + 1. Add this directory to your MANPATH, + + cd Man + MANPATH=$MANPATH:$PWD + man iosnoop + + 2. If the DTraceToolkit has been installed, and that dir to your MANPATH, + + MANPATH=$MANPATH:/opt/DTT/Man + man iosnoop + + 3. Set MANPATH to "." every time you read a script, + + cd Man + MANPATH=. man iosnoop + + 4. Use the -M option to "man", if your OS has it, + + man -M Man iosnoop + + 5. Prentend that you are /usr/bin/man, if your OS has nroff, + + nroff -man Man/man1m/iosnoop.1m | more + + 6. Pretend that you are /usr/bin/nroff, + + more Man/man1m/iosnoop.1m + + 7. Pretend that you have no pagers installed, + + while read line; do echo $line; done < Man/man1m/iosnoop.1m + + 8. Pretend that you can read hex, + + od -x Man/man1m/iosnoop.1m + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/anonpgpid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/anonpgpid.d.1m new file mode 100644 index 000000000000..9cafd4806269 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/anonpgpid.d.1m @@ -0,0 +1,54 @@ +.TH anonpgpid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +anonpgpid.d \- anonymous memory paging info by PID on CPU. Uses DTrace. +.SH SYNOPSIS +.B anonpgpid.d +.SH DESCRIPTION +This scripts may help identify which processes are affected by a system +with low memory, which is paging to the physical swap device. A report +of the process on the CPU when paging occured is printed. + +This program is currently an approximation - often the process when writing +pages to swap will be "pageout" the pageout scanner, or "rcapd" the +resource capping daemon. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Print report after Ctrl-C is hit, +# +.B anonpgpid.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +command name for the process +.TP +D +direction, Read or Write +.TP +BYTES +total bytes during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +anonpgpid.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/bitesize.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/bitesize.d.1m new file mode 100644 index 000000000000..4ef13bec7d8c --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/bitesize.d.1m @@ -0,0 +1,57 @@ +.TH bitesize.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +bitesize.d \- analyse disk I/O size by process. Uses DTrace. +.SH SYNOPSIS +.B bitesize.d +.SH DESCRIPTION +This produces a report for the size of disk events caused by +processes. These are the disk events sent by the block I/O driver. + +If applications must use the disks, we generally prefer they do so +sequentially with large I/O sizes, or larger "bites". + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B bitesize.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +command and argument list +.TP +value +size in bytes +.TP +count +number of I/O operations +.PP +.SH NOTES +The application may be requesting smaller sized operations, which +are being rounded up to the nearest sector size or UFS block size. + +To analyse what the application is requesting, DTraceToolkit programs +such as Proc/fddist may help. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +bitesize.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iosnoop(1M), seeksize(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/connections.1m b/cddl/contrib/dtracetoolkit/Man/man1m/connections.1m new file mode 100644 index 000000000000..ea0285cc55ea --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/connections.1m @@ -0,0 +1,77 @@ +.TH connections 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +connections \- print inbound TCP connections by process. Uses DTrace. +.SH SYNOPSIS +.B connections +[\-htvZ] +.SH DESCRIPTION +This displays the PID and command name of the processes accepting +connections, along with the source IP address and destination port number + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH OPTIONS +.TP +\-t +print timestamps, us +.TP +\-v +print timestamps, string +.TP +\-Z +print zonename +.PP +.SH EXAMPLES +.TP +snoop inbound connections +# +.B connections +.TP +snoop connections with time +# +.B connections +\-v +.PP +.SH FIELDS +.TP +UID +user ID of the server +.TP +PID +process ID of the server +.TP +CMD +server command name +.TP +TIME +timestamp, us +.TP +TIMESTR +timestamp, string +.TP +PORT +server port +.TP +IP_SOURCE +source IP of the client, written in IPv4 style +.TP +ZONE +zonename +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +connections will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), snoop(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/cpudists.1m b/cddl/contrib/dtracetoolkit/Man/man1m/cpudists.1m new file mode 100644 index 000000000000..aeb29ca6a8f5 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/cpudists.1m @@ -0,0 +1,86 @@ +.TH cpudists 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +cpudists \- CPU distrib. by Kernel/Idle/Process. Uses DTrace. +.SH SYNOPSIS +.B cpudists +[\-ahV] [\-t top] [interval [count]] +.SH DESCRIPTION +cpudists prints the CPU time distributions consumed by the Kernel, +Idle threads and by Processes. + +This program is a variant on cputimes, and creates extra kernel load as +described in cputimes(1M). cpudists prints out a distribution report +(a quantize aggregation), such that the number of occurrences and +duration of each thread using the CPUs can be identified. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo and sched providers. +.SH OPTIONS +.TP +\-a +print all processes +.TP +\-T +print totals +.TP +\-V +don't print timestamps +.TP +\-t num +print top num lines only +.SH EXAMPLES +.TP +Default, print Kernel/Idle/Process time, 1 x 1 second sample, +# +.B cpudists +.PP +.TP +Print every 1 second, +# +.B cpudists +1 +.PP +.TP +Print all processes every 10 seconds, +# +.B cpudists +\-a 10 +.PP +.TP +Print top 8 lines every 5 seconds, +# +.B cpudists +\-at 8 5 +.PP +.SH FIELDS +.TP +IDLE +Idle time - CPU running idle thread +.TP +KERNEL +Kernel time - Kernel servicing interrupts, ... +.TP +PROCESS +Process time - PIDs running on the system +.TP +value +Time in nanoseconds +.TP +count +Number of occurrences that were at least this duration (ns) +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +cpudists will run once, unless a count is specified. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), vmstat(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/cputimes.1m b/cddl/contrib/dtracetoolkit/Man/man1m/cputimes.1m new file mode 100644 index 000000000000..bcafbb106589 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/cputimes.1m @@ -0,0 +1,87 @@ +.TH cputimes 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +cputimes \- print time by Kernel/Idle/Process. Uses DTrace. +.SH SYNOPSIS +.B cputimes +[\-ahTV] [\-t top] [interval [count]] +.SH DESCRIPTION +cputimes prints the CPU time consumed by the Kernel, Idle threads and +by Processes. + +This program accurately measures time consumed by the kernel, but in +doing so creates extra kernel load of it's own. This extra kernel +activity can be measured by running one cputimes and then another, and +comparing the difference in kernel consumed time. This method can be +used to estimate the load caused by other DTrace scripts. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo and sched providers. +.SH OPTIONS +.TP +\-a +print all processes +.TP +\-T +print totals +.TP +\-V +don't print timestamps +.TP +\-t num +print top num lines only +.SH EXAMPLES +.TP +Default, print Kernel/Idle/Process time, 1 x 1 second sample, +# +.B cputimes +.PP +.TP +Print every 1 second, +# +.B cputimes +1 +.PP +.TP +Print all processes every 10 seconds, +# +.B cputimes +\-a 10 +.PP +.TP +Print top 8 lines every 5 seconds, +# +.B cputimes +\-at 8 5 +.PP +.SH FIELDS +.TP +THREADS +Either KERNEL, IDLE, PROCESS or process name. +.TP +IDLE +Idle time - CPU running idle thread +.TP +KERNEL +Kernel time - Kernel servicing interrupts, ... +.TP +PROCESS +Process time - PIDs running on the system +.TP +TIME (ns) +Sum of the CPU time, ns (nanoseconds) +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +cputimes will run once, unless a count is specified. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), vmstat(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/cputypes.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/cputypes.d.1m new file mode 100644 index 000000000000..82b6fecdccaa --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/cputypes.d.1m @@ -0,0 +1,54 @@ +.TH cputypes.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +cputypes.d \- list CPU types. Uses DTrace. +.SH SYNOPSIS +.B cputypes.d +.SH DESCRIPTION +This program lists CPU type information for the online CPUs +in the system. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable. +.SH EXAMPLES +.TP +List CPU types, +# +.B cputypes.d +.PP +.SH FIELDS +.TP +CPU +CPU ID +.TP +CHIP +chip ID +.TP +PSET +processor set ID +.TP +LGRP +latency group ID +.TP +CLOCK +clock speed, MHz +.TP +TYPE +CPU type +.TP +FPU +floating point identifier type +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +psrinfo(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/cpuwalk.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/cpuwalk.d.1m new file mode 100644 index 000000000000..16874d988e39 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/cpuwalk.d.1m @@ -0,0 +1,53 @@ +.TH cpuwalk.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +cpuwalk.d \- Measure which CPUs a process runs on. Uses DTrace. +.SH SYNOPSIS +.B cpuwalk.d [duration] +.SH DESCRIPTION +This program is for multi-CPU servers, and can help identify if a process +is running on multiple CPUs concurrently or not. + +A duration may be specified in seconds. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Any +.SH STABILITY +stable. +.SH EXAMPLES +.TP +this runs until Ctrl\-C is hit, +# +.B cpuwalk.d +.PP +.TP +run for 5 seconds, +# +.B cpuwalk.d +5 +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +value +CPU id +.TP +count +number of samples (sample at 100 hz) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +cpuwalk.d will run until Ctrl\-C is hit, or the duration specified +is reached. +.SH SEE ALSO +threaded.d(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/crash.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/crash.d.1m new file mode 100644 index 000000000000..368229b133ec --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/crash.d.1m @@ -0,0 +1,81 @@ +.TH crash.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +crash.d \- Crashed Application info. Uses DTrace. +.SH SYNOPSIS +.B crash.d +.SH DESCRIPTION +crash.d monitors for applications that crash. +When a crash via a SIGSEGV or SIGBUS is detected, a report of the +process state is printed out. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the proc provider, and uses /usr/bin/prun. +.SH FIELDS +.TP +Type +signal type +.TP +Program +execname of process +.TP +Args +argument listing of process +.TP +PID +process ID +.TP +TID +thread ID +.TP +LWPs +number of Light Weight Processes +.TP +PPID +parent process ID +.TP +UID +user ID +.TP +TaskID +task ID +.TP +ProjID +project ID +.TP +PoolID +pool ID +.TP +ZoneID +zone ID +.TP +zone +zone name +.TP +CWD +current working directory +.TP +errno +error number of last syscall +.PP +.SH EXAMPLES +.TP +Monitor for crashing applications. +# +.B crash.d +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +crash.d will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/creatbyproc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/creatbyproc.d.1m new file mode 100644 index 000000000000..fe4f12363705 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/creatbyproc.d.1m @@ -0,0 +1,55 @@ +.TH creatbyproc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +creatbyproc.d \- snoop creat()s by process name. Uses DTrace. +.SH SYNOPSIS +.B creatbyproc.d +.SH DESCRIPTION +creatbyproc.d is a DTrace OneLiner to print file creations as it +occurs, including the name of the process calling the open. + +This matches file creates from the creat() system call; not all +file creation occurs in this way, sometimes it is through open() +with a O_CREAT flag, this script will not monitor that activity. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +This prints process names and new pathnames until Ctrl\-C is hit. +# +.B creatbyproc.d +.PP +.SH FIELDS +.TP +CPU +The CPU that recieved the event +.TP +ID +A DTrace probe ID for the event +.TP +FUNCTION:NAME +The DTrace probe name for the event +.TP +remaining fields +The first is the name of the process, the second is the file pathname. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +creatbyproc.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/cswstat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/cswstat.d.1m new file mode 100644 index 000000000000..7256d5f315d9 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/cswstat.d.1m @@ -0,0 +1,51 @@ +.TH cswstat.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +cswstat.d \- context switch time stats. Uses DTrace. +.SH SYNOPSIS +.B cswstat.d +.SH DESCRIPTION +cswstat.d is a DTrace program to print context switch time +statistics. + +This program measures the time consumed during context switching, +and prints it with the number of context switches and the average +time. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sched provider. +.SH EXAMPLES +.TP +Print statistics every second, +# +.B cswstat.d +.PP +.SH FIELDS +.TP +TIME +The current time +.TP +NUM +Number of context switches in this sample +.TP +CSWTIME +Total time consumed context switching, us +.TP +AVGTIME +Average time for each context switch, us +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +cswstat.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +mpstat(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dappprof.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dappprof.1m new file mode 100644 index 000000000000..de1b52a7fa2f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dappprof.1m @@ -0,0 +1,98 @@ +.TH dappprof 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dappprof \- profile user and lib function usage. Uses DTrace. +.SH SYNOPSIS +.B dappprof +[\-acehoTU] [\-u lib] { \-p PID | command } +.SH DESCRIPTION +dappprof prints details on user and library call times for processes +as a summary style aggragation. By default the user fuctions are +traced, options can be used to trace library activity. Output can +include function counts, elapsed times and on cpu times. + +The elapsed times are interesting, to help identify functions +that take some time to complete (during which the process may +have slept). CPU time helps us identify syscalls that +are consuming CPU cycles to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the pid provider. +.SH OPTIONS +.TP +\-a +print all data +.TP +\-c +print function counts +.TP +\-e +print elapsed times, ns +.TP +\-o +print CPU times, ns +.TP +\-T +print totals +.TP +\-p PID +examine this PID +.TP +\-u lib +trace this library instead +.TP +\-U +trace all library and user functions +.PP +.SH EXAMPLES +.TP +run and examine the "df \-h" command, +# +.B dappprof +df \-h +.PP +.TP +print elapsed times, on-cpu times and counts for "df \-h", +# +.B dappprof +-ceo df \-h +.TP +print elapsed times for PID 1871, +# +.B dappprof +\-p 1871 +.PP +.TP +print all data for PID 1871, +# +.B dappprof +\-ap 1871 +.PP +.SH FIELDS +.TP +CALL +Function call name +.TP +ELAPSED +Total elapsed time, nanoseconds +.TP +CPU +Total on-cpu time, nanoseconds +.TP +COUNT +Number of occurrences +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +dappprof will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dapptrace(1M), dtrace(1M), apptrace(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dapptrace.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dapptrace.1m new file mode 100644 index 000000000000..c439f05380c8 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dapptrace.1m @@ -0,0 +1,112 @@ +.TH dapptrace 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dapptrace \- trace user and library function usage. Uses DTrace. +.SH SYNOPSIS +.B dapptrace +[\-acdeFlhoU] [\-u lib] { \-p PID | command } +.SH DESCRIPTION +dapptrace prints details on user and library function calls. By +default it traces user functions only, options can be used to +trace library activity. + +Of particular interest is the elapsed times and on cpu times, which +can identify both function calls that are slow to complete, and those +which are consuming CPU cycles. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the pid provider. +.SH OPTIONS +.TP +\-a +print all details +.TP +\-b bufsize +dynamic variable buffer size. Increase this if you notice dynamic +variable drop errors. The default is "4m" for 4 megabytes per CPU. +.TP +\-c +print function call counts +.TP +\-d +print relative timestamps, us +.TP +\-e +print elapsed times, us +.TP +\-F +print flow indentation +.TP +\-l +force printing of pid/lwpid per line +.TP +\-o +print on-cpu times, us +.TP +\-p PID +examine this PID +.TP +\-u lib +trace this library instead +.TP +\-U +trace all library and user functions +.PP +.SH EXAMPLES +.TP +run and examine the "df -h" command, +# +.B dapptrace +df -h +.PP +.TP +examine PID 1871, +# +.B dapptrace +\-p 1871 +.PP +.TP +print using flow indents, +# +.B dapptrace +\-Fp 1871 +.PP +.TP +print elapsed and CPU times, +# +.B dapptrace +\-eop 1871 +.PP +.SH FIELDS +.TP +PID/LWPID +Process ID / Lightweight Process ID +.TP +RELATIVE +relative timestamps to the start of the thread, us (microseconds) +.TP +ELAPSD +elapsed time for this system call, us +.TP +CPU +on-cpu time for this system call, us +.TP +CALL(args) +function call name, with some arguments in hexadecimal +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +dapptrace will run forever until Ctrl\-C is hit, or if a command was +executed dapptrace will finish when the command ends. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dappprof(1M), dtrace(1M), apptrace(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dexplorer.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dexplorer.1m new file mode 100644 index 000000000000..10683a936542 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dexplorer.1m @@ -0,0 +1,64 @@ +.TH dexplorer 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dexplorer \- run a series of scripts and archive output. Uses DTrace. +.SH SYNOPSIS +.B dexplorer +.SH DESCRIPTION +This program automatically runs a collection of DTrace scripts to examine +many areas of the system, and places the output in a meaningful directory +structure that is tar'd and gzip'd. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH OPTIONS +.TP +\-q +quiet mode +.TP +\-y +"yes", don't prompt for confirmation +.TP +\-D +don't delete output dir +.TP +\-T +don't create output tar.gz +.TP +\-d outputdir +output directory +.TP +\-i interval +interval for each sample +.PP +.SH EXAMPLES +.TP +Create output file in current directory, +# +.B dexplorer +.TP +Don't prompt +# +.B dexplorer +\-y +.TP +Leave expanded directories, don't archive and compress, +# +.B dexplorer +\-DT +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/diskhits.1m b/cddl/contrib/dtracetoolkit/Man/man1m/diskhits.1m new file mode 100644 index 000000000000..e8b9c57e1bcd --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/diskhits.1m @@ -0,0 +1,46 @@ +.TH diskhits 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +diskhits \- disk access by file offset. Uses DTrace. +.SH SYNOPSIS +.B diskhits pathname +.SH DESCRIPTION +This prints how a file was accessed, the locations on a distribution plot. +This is for the cache misses only - the file activity that resulted in +disk events. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH EXAMPLES +.TP +Sample /var/adm/messages disk activity, +# +.B diskhits /var/adm/messages +.PP +.SH FIELDS +.TP +Location (KB) +the file offset of the disk activity, Kbytes +.TP +Size (KB) +size of the disk activity, Kbytes +.TP +Total RW +Total disk activity, reads + writes +.PP +.SH BASED ON +/usr/demo/dtrace/applicat.d +.PP +.SH DOCUMENTATION +DTrace Guide "io Provider" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +diskhits will sample until Ctrl\-C is hit. +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dispqlen.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dispqlen.d.1m new file mode 100644 index 000000000000..dcc08200d8f9 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dispqlen.d.1m @@ -0,0 +1,36 @@ +.TH dispqlen.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dispqlen.d \- dispatcher queue length by CPU. Uses DTrace. +.SH SYNOPSIS +.B dispqlen.d +.SH DESCRIPTION +The dispatcher queue length is an indication of CPU saturation. +It is not an indicatior of utilisation - the CPUs may or may not be +utilised when the dispatcher queue reports a length of zero. + +This script measures this activity by sampling at 1000 Hertz per CPU. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - walks private kernel structs. +.SH EXAMPLES +.TP +Print dispatcher queue length by CPU. +# +.B dispqlen.d +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +dispqlen.d will sample until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +uptime(1), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dnlcps.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dnlcps.d.1m new file mode 100644 index 000000000000..482fd0747cc0 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dnlcps.d.1m @@ -0,0 +1,51 @@ +.TH dnlcps.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dnlcps.d \- DNLC stats by process. Uses DTrace. +.SH SYNOPSIS +.B dnlcps.d +.SH DESCRIPTION +The DNLC is the Directory Name Lookup Cache. Filename lookups often +return a hit from here, before needing to traverse the regular file +system cache or go to disk. + +dnlcps.d prints DNLC statistics by process. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B dnlcps.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +command name +.TP +value +0 == miss, 1 == hit +.TP +count +number of occurrences +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +dnlcps.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dnlcsnoop.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dnlcsnoop.d.1m new file mode 100644 index 000000000000..cd9ac7be9461 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dnlcsnoop.d.1m @@ -0,0 +1,52 @@ +.TH dnlcsnoop.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dnlcsnoop.d \- snoop DNLC activity. Uses DTrace. +.SH SYNOPSIS +.B dnlcsnoop.d +.SH DESCRIPTION +The DNLC is the Directory Name Lookup Cache. Filename lookups often +return a hit from here, before needing to traverse the regular file +system cache or go to disk. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B dnlcsnoop.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +command name +.TP +TIME +Elapsed time for lookup, us +.TP +HIT +DNLC hit Y/N +.TP +PATH +Path for DNLC lookup +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +dnlcsnoop.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dnlcstat.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dnlcstat.1m new file mode 100644 index 000000000000..146c39dc1d96 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dnlcstat.1m @@ -0,0 +1,57 @@ +.TH dnlcstat 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dnlcstat \- DNLC statistics. Uses DTrace. +.SH SYNOPSIS +.B dnlcstat +[interval [count]] +.SH DESCRIPTION +The DNLC is the Directory Name Lookup Cache. Filename lookups often +return a hit from here, before needing to traverse the regular file +system cache or go to disk. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Print DNLC statistics every second, +# +.B dnlcstat +.TP +Print every 5 seconds, 6 times, +# +.B dnlcstat +5 6 +.PP +.SH FIELDS +.TP +%hit +hit percentage for this sample +.TP +hit +number of DNLC hits in this sample +.TP +miss +number of DNLC misses in this sample +.PP +.SH NOTES +See the CacheKit, http://www.brendangregg.com/cachekit.html for a version +of dnlcstat written in Perl (Kstat) that uses much less CPU. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +dnlcstat will run until Ctrl\-C is hit, or until the count argument +has been satisfied. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dtruss.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dtruss.1m new file mode 100644 index 000000000000..7837f0e7b5ed --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dtruss.1m @@ -0,0 +1,123 @@ +.TH dtruss 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dtruss \- process syscall details. Uses DTrace. +.SH SYNOPSIS +.B dtruss +[\-acdeflhoLs] [\-t syscall] { \-p PID | \-n name | command } +.SH DESCRIPTION +dtruss prints details on process system calls. It is like a DTrace +version of truss, and has been designed to be less intrusive than +truss. + +Of particular interest is the elapsed times and on cpu times, which +can identify both system calls that are slow to complete, and those +which are consuming CPU cycles. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH OPTIONS +.TP +\-a +print all details +.TP +\-b bufsize +dynamic variable buffer size. Increase this if you notice dynamic +variable drop errors. The default is "4m" for 4 megabytes per CPU. +.TP +\-c +print system call counts +.TP +\-d +print relative timestamps, us +.TP +\-e +print elapsed times, us +.TP +\-f +follow children as they are forked +.TP +\-l +force printing of pid/lwpid per line +.TP +\-L +don't print pid/lwpid per line +.TP +\-n name +examine processes with this name +.TP +\-o +print on-cpu times, us +.TP +\-s +print stack backtraces +.TP +\-p PID +examine this PID +.TP +\-t syscall +examine this syscall only +.PP +.SH EXAMPLES +.TP +run and examine the "df -h" command +# +.B dtruss +df -h +.PP +.TP +examine PID 1871 +# +.B dtruss +\-p 1871 +.PP +.TP +examine all processes called "tar" +# +.B dtruss +\-n tar +.PP +.TP +run test.sh and follow children +# +.B dtruss +\-f test.sh +.TP +run the "date" command and print elapsed and on cpu times, +# +.B dtruss +\-eo date +.PP +.SH FIELDS +.TP +PID/LWPID +Process ID / Lightweight Process ID +.TP +RELATIVE +relative timestamps to the start of the thread, us (microseconds) +.TP +ELAPSD +elapsed time for this system call, us +.TP +CPU +on-cpu time for this system call, us +.TP +SYSCALL(args) +system call name, with arguments (some may be evaluated) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +dtruss will run forever until Ctrl\-C is hit, or if a command was +executed dtruss will finish when the command ends. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +procsystime(1M), dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/dvmstat.1m b/cddl/contrib/dtracetoolkit/Man/man1m/dvmstat.1m new file mode 100644 index 000000000000..20fa955e0d71 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/dvmstat.1m @@ -0,0 +1,93 @@ +.TH dvmstat 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +dvmstat \- vmstat by PID/name/command. Uses DTrace. +.SH SYNOPSIS +.B dvmstat +{ \-p PID | \-n name | command } +.SH DESCRIPTION +This program provides vmstat like data for one particular PID, a +process name, or when running a command. It prints statistics +every second. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the vminfo provider. +.SH OPTIONS +.TP +\-p PID +examine this Process ID +.TP +\-n name +examine processes with this name +.PP +.SH EXAMPLES +.TP +examine PID 1871, +# +.B dvmstat +\-p 1871 +.TP +examine processes called "tar", +# +.B dvmstat +\-n tar +.TP +run and examine "df -h", +# +.B dvmstat +df -h +.PP +.SH FIELDS +.TP +re +page reclaims, Kbytes +.TP +maj +major faults, Kbytes +.TP +mf +minor faults, Kbytes +.TP +fr +page frees, Kbytes +.TP +epi +executable page ins, Kbytes +.TP +epo +executable page outs, Kbytes +.TP +api +anonymous page ins, Kbytes +.TP +apo +anonymous page outs, Kbytes +.TP +fpi +filesystem page ins, Kbytes +.TP +fpo +filesystem page outs, Kbytes +.TP +sy +system calls, number +.PP +.SH NOTES +Most of the statistics are in units of kilobytes, unlike the +original vmstat command which sometimes uses pages. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +dvmstat will run until Ctrl\-C is hit, or the command it is +examining ends. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), vmstat(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/errinfo.1m b/cddl/contrib/dtracetoolkit/Man/man1m/errinfo.1m new file mode 100644 index 000000000000..6b63e5211192 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/errinfo.1m @@ -0,0 +1,85 @@ +.TH errinfo 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +errinfo \- print errno for syscall fails. Uses DTrace. +.SH SYNOPSIS +.B errinfo +[\-a|\-A|\-hsvZ] [\-c command] +.SH DESCRIPTION +errinfo snoops syscall failures and prints the errno value and +description of the error number. + +This program can help determine if applications are silently +failing, providing some details on the cause. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH OPTIONS +.TP +\-c +counts - print an aggregate style report containing a +frequency count of errors +.TP +\-p PID +examine this PID only +.TP +\-n name +examine processes with ths name only (eg, "ls") +.SH EXAMPLES +.TP +Default output, print errors as they occur, +# +.B errinfo +.PP +.TP +Print a frequency count report, +# +.B errinfo +\-c +.PP +.TP +Snoop errors as they occur for "ssh" processes, +# +.B errinfo +\-n ssh +PP +.TP +Snoop errors for PID 81 only, +# +.B errinfo +\-p 81 +.PP +.SH FIELDS +.TP +EXEC +Program name (truncated) +.TP +SYSCALL +System call name +.TP +ERR +Value of errno +.TP +DESC +Description of errno message +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +errinfo will run forever until Ctrl\-C is hit. +.SH FILES +.TP +/usr/include/sys/errno.h +Contains the full descriptions for the error numbers. +.PP +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/execsnoop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/execsnoop.1m new file mode 100644 index 000000000000..a7114cec58d0 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/execsnoop.1m @@ -0,0 +1,108 @@ +.TH execsnoop 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +execsnoop \- snoop new process execution. Uses DTrace. +.SH SYNOPSIS +.B execsnoop +[\-a|\-A|\-ejhsvZ] [\-c command] +.SH DESCRIPTION +execsnoop prints details of new processes as they are executed. +Details such as UID, PID and argument listing are printed out. + +This program is very useful to examine short lived processes that would +not normally appear in a prstat or "ps -ef" listing. Sometimes +applications will run hundreds of short lived processes in their +normal startup cycle, a behaviour that is easily monitored with execsnoop. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH OPTIONS +.TP +\-a +print all data +.TP +\-A +dump all data, space delimited +.TP +\-e +safe output, parseable. This prevents the ARGS field containing "\\n"s, +to assist postprocessing. +.TP +\-j +print project ID +.TP +\-s +print start time, us +.TP +\-v +print start time, string +.TP +\-Z +print zonename +.TP +\-c command +command name to snoop +.SH EXAMPLES +.TP +Default output, print processes as they are executed, +# +.B execsnoop +.TP +Print human readable timestamps, +# +.B execsnoop +\-v +.TP +Print zonename, +# +.B execsnoop +\-Z +.TP +Snoop this command only, +# +.B execsnoop +\-f ls +.PP +.SH FIELDS +.TP +UID +User ID +.TP +PID +Process ID +.TP +PPID +Parent Process ID +.TP +COMM +command name for the process +.TP +ARGS +argument listing for the process +.TP +ZONE +zonename +.TP +PROJ +project ID +.TP +TIME +timestamp for the exec event, us +.TP +STRTIME +timestamp for the exec event, string +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +execsnoop will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/fddist.1m b/cddl/contrib/dtracetoolkit/Man/man1m/fddist.1m new file mode 100644 index 000000000000..990d76174386 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/fddist.1m @@ -0,0 +1,63 @@ +.TH fddist 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +fddist \- file descriptor usage distributions. Uses DTrace. +.SH SYNOPSIS +.B fddist [\-r|\-w] +.SH DESCRIPTION +This prints distributions for read and write events by file descriptor, +by process. This can be used to determine which file descriptor a +process is doing the most I/O with. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH OPTIONS +.TP +\-r +reads only +.TP +\-w +writes only +.PP +.SH EXAMPLES +.TP +Sample both read and write activity, +# +.B fddist +.TP +Sample reads only, +# +.B fddist +\-r +.PP +.SH FIELDS +.TP +EXEC +process name +.TP +PID +process ID +.TP +value +file descriptor +.TP +count +number of events +.PP +.SH BASED ON +/usr/demo/dtrace/lquantize.d +.PP +.SH DOCUMENTATION +DTrace Guide "Aggregations" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +fddist will sample until Ctrl\-C is hit. +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/filebyproc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/filebyproc.d.1m new file mode 100644 index 000000000000..23b56481662b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/filebyproc.d.1m @@ -0,0 +1,56 @@ +.TH filebyproc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +filebyproc.d \- snoop opens by process name. Uses DTrace. +.SH SYNOPSIS +.B filebyproc.d +.SH DESCRIPTION +filebyproc.d is a DTrace OneLiner to print file pathnames as they are +opened, including the name of the process calling the open. +A line will be printed regardless of whether the open is actually +successful or not. + +This is useful to learn which files applications are attempting to +open, such as config files, database files, log files, etc. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +This prints new process name and pathnames until Ctrl\-C is hit. +# +.B filebyproc.d +.PP +.SH FIELDS +.TP +CPU +The CPU that recieved the event +.TP +ID +A DTrace probe ID for the event +.TP +FUNCTION:NAME +The DTrace probe name for the event +.TP +remaining fields +The first is the name of the process, the second is the file pathname. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +filebyproc.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +opensnoop(1M), dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/fspaging.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/fspaging.d.1m new file mode 100644 index 000000000000..6911ac5582dd --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/fspaging.d.1m @@ -0,0 +1,88 @@ +.TH fspaging.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +fspaging.d \- file system read/write and paging tracing. Uses DTrace. +.SH SYNOPSIS +.B fspaging.d +.SH DESCRIPTION +This traces file related activity: system call reads and writes, +vnode logical read and writes (fop), vnode putpage and getpage activity, +and disk I/O. It can be used to examine the behaviour of each I/O +layer, from the syscall interface to what the disk is doing. Behaviour +such as read-ahead, and max I/O size breakup can be observed. + +This is a verbose version of fsrw.d, as this also traces paging activity. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Trace file system read/write/paging events, +# +.B fspaging.d +.PP +.SH FIELDS +.TP +Event +traced event (see EVENTS below) +.TP +Device +device, for disk I/O +.TP +RW +either Read or Write +.TP +Size +size of I/O in bytes +.TP +Offset +offset of I/O in kilobytes +.TP +Path +path to file on disk +.PP +.SH EVENTS +.TP +sc-read +system call read +.TP +sc-write +system call write +.TP +fop_read +logical read +.TP +fop_write +logical write +.TP +fop_getpage +logical get page +.TP +fop_putpage +logical put page +.TP +disk_io +physical disk I/O +.TP +disk_ra +physical disk I/O, read ahead +.PP +.SH IDEA +Richard McDougall, Solaris Internals 2nd Ed, FS Chapter. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +fspaging.d will trace until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +fsrw.d(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/fsrw.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/fsrw.d.1m new file mode 100644 index 000000000000..4389c211f063 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/fsrw.d.1m @@ -0,0 +1,80 @@ +.TH fsrw.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +fsrw.d \- file system read/write event tracing. Uses DTrace. +.SH SYNOPSIS +.B fsrw.d +.SH DESCRIPTION +This traces file related activity: system call reads and writes, +vnode logical read and writes (fop), and disk I/O. It can be used +to examine the behaviour of each I/O layer, from the syscall +interface to what the disk is doing. Behaviour such as read-ahead, and +max I/O size breakup can be observed. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Trace file system read/write events, +# +.B fsrw.d +.PP +.SH FIELDS +.TP +Event +traced event (see EVENTS below) +.TP +Device +device, for disk I/O +.TP +RW +either Read or Write +.TP +Size +size of I/O in bytes +.TP +Offset +offset of I/O in kilobytes +.TP +Path +path to file on disk +.PP +.SH EVENTS +.TP +sc-read +system call read +.TP +sc-write +system call write +.TP +fop_read +logical read +.TP +fop_write +logical write +.TP +disk_io +physical disk I/O +.TP +disk_ra +physical disk I/O, read ahead +.PP +.SH IDEA +Richard McDougall, Solaris Internals 2nd Ed, FS Chapter. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +fsrw.d will trace until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +fspaging.d(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/guess.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/guess.d.1m new file mode 100644 index 000000000000..4c6d2e2ea472 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/guess.d.1m @@ -0,0 +1,37 @@ +.TH guess.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +guess.d \- guessing game. Uses DTrace. +.SH SYNOPSIS +.B guess.d +.SH DESCRIPTION +This is written to demonstrate this language versus the same program +written in other languages. + +See http://www.brendangregg.com/guessinggame.html + +It exists in the DTraceToolkit as a curiosity, rather than something +actually useful. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +Play the game, +# +.B guess.d +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +guess.d will only exit when you win the game. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/hotkernel.1m b/cddl/contrib/dtracetoolkit/Man/man1m/hotkernel.1m new file mode 100644 index 000000000000..49772b6ae1ee --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/hotkernel.1m @@ -0,0 +1,39 @@ +.TH hotkernel 1m "$Date:: 2007-09-24 #$" "USER COMMANDS" +.SH NAME +hotkernel - sample on-CPU kernel-level functions and modules. +.SH SYNOPSIS +.B hotkernel +[\-hm] +.SH DESCRIPTION +This samples the on-CPU function at 1001 Hertz, for a simple yet +effective kernel-level profiling tool for sampling exclusive function time. +The output will identify which function is on the CPU the most - which is +the hottest. See Notes/ALLexclusive_notes.txt for an explanation of +exclusive time. +.SH OS +Solaris +.SH STABILITY +stable - Written using Perl and DTrace (Solaris 10 03/05) +.SH EXAMPLES +.TP +Sample kernel functions, +# +.B hotkernel +.PP +.TP +Sample kernel modules, +# +.B hotkernel +\-m +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +hotkernel will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M), hotuser(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/hotspot.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/hotspot.d.1m new file mode 100644 index 000000000000..a99a589cc92d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/hotspot.d.1m @@ -0,0 +1,51 @@ +.TH hotspot.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +hotspot.d \- print disk event by location. Uses DTrace. +.SH SYNOPSIS +.B hotspot.d +.SH DESCRIPTION +hotspot.d is a simple DTrace script to determine if disk activity is +occuring in the one place - a "hotspot". This helps us understand the +system's usage of a disk, it does not imply that the existance or not +of a hotspot is good or bad (often may be good, less seeking). + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B hotspot.d +.PP +.SH FIELDS +.TP +Disk +disk instance name +.TP +Major +driver major number +.TP +Minor +driver minor number +.TP +value +location of disk event, megabytes +.TP +count +number of events +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +hotspot.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/hotuser.1m b/cddl/contrib/dtracetoolkit/Man/man1m/hotuser.1m new file mode 100644 index 000000000000..ab26523755cc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/hotuser.1m @@ -0,0 +1,44 @@ +.TH hotuser 1m "$Date:: 2007-09-24 #$" "USER COMMANDS" +.SH NAME +hotuser - sample on-CPU user-level functions and libraries. +.SH SYNOPSIS +.B hotuser +[\-hl] { \-c command | \-p PID } +.SH DESCRIPTION +This samples the on-CPU function at 1001 Hertz, for a simple yet +effective user-level profiling tool for sampling exclusive function time. +The output will identify which function is on the CPU the most - which +is the hottest. See Notes/ALLexclusive_notes.txt for an explanation of +exclusive time. +.SH OS +Solaris +.SH STABILITY +stable - Written using Perl and DTrace (Solaris 10 03/05) +.SH EXAMPLES +.TP +Sample user functions from PID 81, +# +.B hotuser +\-p 81 +.TP +Sample user libraries from PID 81, +# +.B hotuser +\-lp 81 +.TP +Sample Xorg, +# +.B hotuser +`pgrep \-n Xorg` +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +hotuser will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M), hotkernel(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/httpdstat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/httpdstat.d.1m new file mode 100644 index 000000000000..5dd0a3fa96a9 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/httpdstat.d.1m @@ -0,0 +1,67 @@ +.TH httpdstat.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +httpdstat.d \- realtime httpd statistics. Uses DTrace. +.SH SYNOPSIS +.B httpdstat.d +[interval [count]] +.SH DESCRIPTION +This prints connection statistics for "httpd" processes, such as those +from an Apache web server. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +Print statistics every second, +# +.B httpdstat.d +.TP +Print every 5 seconds, 6 times, +# +.B httpdstat.d +5 6 +.PP +.SH FIELDS +.TP +TIME +time, string +.TP +NUM +number of connections +.TP +GET +number of GETs +.TP +POST +number of POSTs +.TP +HEAD +number of HEADs +.TP +TRACE +number of TRACEs +.PP +.SH NOTES +All statistics are printed as a value per interval. + +This version does not process subsequent operations on keepalives. +.PP +.SH IDEA +Ryan Matteson +(who first wrote a solution to this). +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +httpdstat.d will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/icmpstat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/icmpstat.d.1m new file mode 100644 index 000000000000..be4b87ae9f97 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/icmpstat.d.1m @@ -0,0 +1,47 @@ +.TH icmpstat.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +icmpstat.d \- print ICMP statistics. Uses DTrace. +.SH SYNOPSIS +.B icmpstat.d +.SH DESCRIPTION +icmpstat.d is a DTrace program to print ICMP statistics every second, +retrieved from the MIB provider. This is a simple script to demonstrate the +ability to trace ICMP events. + +The ICMP statistics are documented in the mib2_icmp struct +in /usr/include/inet/mib2.h; and also in the mib provider +chapter of the DTrace Guide, found at +http://docs.sun.com/db/doc/817-6223. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the mib provider. +.SH EXAMPLES +.TP +Print statistics every second, +# +.B icmpstat.d +.PP +.SH FIELDS +.TP +STATISTIC +ICMP statistic name +.TP +VALUE +total of statistic during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +icmpstat.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/intbycpu.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/intbycpu.d.1m new file mode 100644 index 000000000000..79314dc4c268 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/intbycpu.d.1m @@ -0,0 +1,48 @@ +.TH intbycpu.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +intbycpu.d \- interrupts by CPU. Uses DTrace. +.SH SYNOPSIS +.B intbycpu.d +.SH DESCRIPTION +intbycpu.d is based on a DTrace OneLiner to a report of the number of +interrupts by CPU. + +The intrstat(1M) command can be used for further analysis +of interrputs. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sdt provider interrupt probes. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B intbycpu.d +.PP +.SH FIELDS +.TP +CPU +This is the CPU id. +.TP +INTERRUPTS +This is the number of interrputs received in the sample. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +intbycpu.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +intrstat(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/intoncpu.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/intoncpu.d.1m new file mode 100644 index 000000000000..ec52b815236d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/intoncpu.d.1m @@ -0,0 +1,42 @@ +.TH intoncpu.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +intoncpu.d \- print interrput on-cpu usage. Uses DTrace. +.SH SYNOPSIS +.B intoncpu.d +.SH DESCRIPTION +This prints a distribution of the on-cpu time for interrput threads. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sdt provider interrupt probes. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B intoncpu.d +.PP +.SH FIELDS +.TP +value +Time interrupt thread was on-cpu, ns +.TP +count +Number of occurrences of at least this time +.PP +.SH BASED ON +/usr/demo/dtrace/intr.d +.PP +.SH DOCUMENTATION +DTrace Guide "sdt Provider" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +intoncpu.d will sample until Ctrl\-C is hit. +.SH SEE ALSO +intrstat(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/inttimes.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/inttimes.d.1m new file mode 100644 index 000000000000..bc6d989aafdc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/inttimes.d.1m @@ -0,0 +1,43 @@ +.TH inttimes.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +inttimes.d \- print interrput on-cpu time total. Uses DTrace. +.SH SYNOPSIS +.B inttimes.d +.SH DESCRIPTION +This prints the total time each driver instance has spent servicing +interrupts. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sdt provider interrupt probes. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B inttimes.d +.PP +.SH FIELDS +.TP +DEVICE +instance name of the device driver +.TP +TIME (ns) +sum of time spent servicing interrupt (nanoseconds) +.PP +.SH BASED ON +/usr/demo/dtrace/intr.d +.PP +.SH DOCUMENTATION +DTrace Guide "sdt Provider" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +inttimes.d will sample until Ctrl\-C is hit. +.SH SEE ALSO +intrstat(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/iofile.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/iofile.d.1m new file mode 100644 index 000000000000..fd3016dd5674 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/iofile.d.1m @@ -0,0 +1,49 @@ +.TH iofile.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +iofile.d \- I/O wait time by file and process. Uses DTrace. +.SH SYNOPSIS +.B iofile.d +.SH DESCRIPTION +This prints the total I/O wait times for each filename by process. +This can help determine why an application is performing poorly by +identifying which file they are waiting on, and the total times. +Both disk and NFS I/O are measured. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B iofile.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +TIME +total wait time for disk events, us +.TP +FILE +file pathname +.PP +.SH BASED ON +/usr/demo/dtrace/iocpu.d +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +iofile.d will sample until Ctrl\-C is hit. +.SH SEE ALSO +iosnoop(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/iofileb.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/iofileb.d.1m new file mode 100644 index 000000000000..56ca3acc83a2 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/iofileb.d.1m @@ -0,0 +1,46 @@ +.TH iofileb.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +iofileb.d \- I/O bytes by file and process. Uses DTrace. +.SH SYNOPSIS +.B iofileb.d +.SH DESCRIPTION +This prints a summary of requested disk activity by pathname, +providing totals of the I/O events in bytes. It is a companion to the +iofile.d script - which prints in terms of I/O wait time, not bytes. +I/O wait time is a better metric for understanding performance issues. +Both disk and NFS I/O are measured. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B iofileb.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +KB +kilobytes of disk I/O +.TP +FILE +file pathname +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +iofileb.d will sample until Ctrl\-C is hit. +.SH SEE ALSO +iofile.d(1M), iosnoop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/iopattern.1m b/cddl/contrib/dtracetoolkit/Man/man1m/iopattern.1m new file mode 100644 index 000000000000..6898f82672a9 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/iopattern.1m @@ -0,0 +1,112 @@ +.TH iopattern 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +iopattern \- print disk I/O pattern. Uses DTrace. +.SH SYNOPSIS +.B iopattern +[\-v] [\-d device] [\-f filename] [\-m mount_point] [interval [count]] +.SH DESCRIPTION +This prints details on the I/O access pattern for the disks, such as +percentage of events that were of a random or sequential nature. +By default totals for all disks are printed. + +An event is considered random when the heads seek. This program prints +the percentage of events that are random. The size of the seek is not +measured - it's either random or not. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH OPTIONS +.TP +\-v +print timestamp, string +.TP +\-d device +instance name to snoop (eg, dad0) +.TP +\-f filename +full pathname of file to snoop +.TP +\-m mount_point +mountpoint for filesystem to snoop +.SH EXAMPLES +.TP +Default output, print I/O summary every 1 second, +# +.B iopattern +.PP +.TP +Print 10 second samples, +# +.B iopattern +10 +.PP +.TP +Print 12 x 5 second samples, +# +.B iopattern +5 12 +.PP +.TP +Snoop events on the root filesystem only, +# +.B iopattern +\-m / +.PP +.SH FIELDS +.TP +%RAN +percentage of events of a random nature +.TP +%SEQ +percentage of events of a sequential nature +.TP +COUNT +number of I/O events +.TP +MIN +minimum I/O event size +.TP +MAX +maximum I/O event size +.TP +AVG +average I/O event size +.TP +KR +total kilobytes read during sample +.TP +KW +total kilobytes written during sample +.TP +DEVICE +device name +.TP +MOUNT +mount point +.TP +FILE +filename (basename) for I/O operation +.TP +TIME +timestamp, string +.PP +.SH IDEA +Ryan Matteson +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +iopattern will run forever until Ctrl\-C is hit, or the +specified count is reached. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iosnoop(1M), iotop(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/iopending.1m b/cddl/contrib/dtracetoolkit/Man/man1m/iopending.1m new file mode 100644 index 000000000000..c31d967e6eef --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/iopending.1m @@ -0,0 +1,89 @@ +.TH iopending 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +iopending \- plot number of pending disk events. Uses DTrace. +.SH SYNOPSIS +.B iopending +[\-c] [\-d device] [\-f filename] [\-m mount_point] [interval [count]] +.SH DESCRIPTION +This samples the number of disk events that are pending and plots a +distribution graph. By doing this the +"serialness" or "parallelness" of disk behaviour can be distinguished. +A high occurance of a pending value of more than 1 is an indication of +saturation. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH OPTIONS +.TP +\-c +clear screen +.TP +\-d device +instance name to snoop (eg, dad0) +.TP +\-f filename +full pathname of file to snoop +.TP +\-m mount_point +mountpoint for filesystem to snoop +.SH EXAMPLES +.TP +Default output, print I/O summary every 1 second, +# +.B iopending +.PP +.TP +Print 10 second samples, +# +.B iopending +10 +.PP +.TP +Print 12 x 5 second samples, +# +.B iopending +5 12 +.PP +.TP +Snoop events on the root filesystem only, +# +.B iopending +\-m / +.PP +.SH FIELDS +.TP +value +number of pending events, 0 == idle +.TP +count +number of samples @ 1000 Hz +.TP +load +1 min load average +.TP +disk_r +total disk read Kb for sample +.TP +disk_w +total disk write Kb for sample +.PP +.SH IDEA +Dr Rex di Bona +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +iopending will run forever until Ctrl\-C is hit, or the +specified count is reached. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iosnoop(1M), iotop(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/iosnoop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/iosnoop.1m new file mode 100644 index 000000000000..6e9058dabf3a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/iosnoop.1m @@ -0,0 +1,167 @@ +.TH iosnoop 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +iosnoop \- snoop I/O events as they occur. Uses DTrace. +.SH SYNOPSIS +.B iosnoop +[\-a|\-A|\-Deghinostv] [\-d device] [\-f filename] [\-m mount_point] +[\-n name] [\-p PID] +.SH DESCRIPTION +iosnoop prints I/O events as they happen, with useful details such +as UID, PID, block number, size, filename, etc. + +This is useful to determine the process responsible for +using the disks, as well as details on what activity the process +is requesting. Behaviour such as random or sequential I/O can +be observed by reading the block numbers. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH OPTIONS +.TP +\-a +print all data +.TP +\-A +dump all data, space delimited +.TP +\-D +print time delta, us (elapsed) +.TP +\-e +print device name +.TP +\-i +print device instance +.TP +\-n +print major and minor numbers +.TP +\-o +print disk delta time, us +.TP +\-s +print start time, us +.TP +\-t +print completion time, us +.TP +\-v +print completion time, string +.TP +\-d device +instance name to snoop (eg, dad0) +.TP +\-f filename +full pathname of file to snoop +.TP +\-m mount_point +mountpoint for filesystem to snoop +.TP +\-n name +process name +.TP +\-p PID +process ID +.PP +.SH EXAMPLES +.TP +Default output, print I/O activity as it occurs, +# +.B iosnoop +.PP +.TP +Print human readable timestamps, +# +.B iosnoop +\-v +.PP +.TP +Print major and minor numbers, +# +.B iosnoop +\-n +.PP +.TP +Snoop events on the root filesystem only, +# +.B iosnoop +\-m / +.PP +.SH FIELDS +.TP +UID +User ID +.TP +PID +Process ID +.TP +PPID +Parent Process ID +.TP +COMM +command name for the process +.TP +ARGS +argument listing for the process +.TP +SIZE +size of the operation, bytes +.TP +BLOCK +disk block for the operation (location. relative to this filesystem. +more useful with the -n option to print major and minor numbers) +.TP +STIME +timestamp for the disk request, us +.TP +TIME +timestamp for the disk completion, us +.TP +DELTA +elapsed time from request to completion, us (this is the elapsed +time from the disk request (strategy) to the disk completion (iodone)) +.TP +DTIME +time for disk to complete request, us (this is the time for the +disk to complete that event since it's last event (time between iodones), +or, the time to the strategy if the disk had been idle) +.TP +STRTIME +timestamp for the disk completion, string +.TP +DEVICE +device name +.TP +INS +device instance number +.TP +D +direction, Read or Write +.TP +MOUNT +mount point +.TP +FILE +filename (basename) for I/O operation +.PP +.SH NOTES +When filtering on PID or process name, be aware that poor disk event +times may be due to events that have been filtered away, for example +another process that may be seeking the disk heads elsewhere. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +iosnoop will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iotop(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/iotop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/iotop.1m new file mode 100644 index 000000000000..80522436ec84 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/iotop.1m @@ -0,0 +1,154 @@ +.TH iotop 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +iotop \- display top disk I/O events by process. Uses DTrace. +.SH SYNOPSIS +.B iotop +[\-C] [\-D|\-o|\-P] [\-j|\-Z] [\-d device] [\-f filename] +[\-m mount_point] [\-t top] [interval [count]] +.SH DESCRIPTION +iotop tracks disk I/O by process, and prints a summary report that +is refreshed every interval. + +This is measuring disk events that have made it past system caches. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH OPTIONS +.TP +\-C +don't clear the screen +.TP +\-D +print delta times - elapsed, us +.TP +\-j +print project ID +.TP +\-o +print disk delta times, us +.TP +\-P +print %I/O (disk delta times) +.TP +\-Z +print zone ID +.TP +\-d device +instance name to snoop (eg, dad0) +.TP +\-f filename +full pathname of file to snoop +.TP +\-m mount_point +mountpoint for filesystem to snoop +.TP +\-t top +print top number only +.PP +.SH EXAMPLES +.TP +Default output, print summary every 5 seconds +# +.B iotop +.PP +.TP +One second samples, +# +.B iotop +1 +.PP +.TP +print %I/O (time based), +# +.B iotop +\-P +.PP +.TP +Snoop events on the root filesystem only, +# +.B iotop +\-m / +.TP +Print top 20 lines only, +# +.B iotop +\-t 20 +.TP +Print 12 x 5 second samples, scrolling, +# +.B iotop +\-C 5 12 +.PP +.SH FIELDS +.TP +UID +user ID +.TP +PID +process ID +.TP +PPID +parent process ID +.TP +PROJ +project ID +.TP +ZONE +zone ID +.TP +CMD +command name for the process +.TP +DEVICE +device name +.TP +MAJ +device major number +.TP +MIN +device minor number +.TP +D +direction, Read or Write +.TP +BYTES +total size of operations, bytes +.TP +ELAPSED +total elapsed times from request to completion, us (this is the elapsed +time from the disk request (strategy) to the disk completion (iodone)) +.TP +DISKTIME +total times for disk to complete request, us (this is the time for the +disk to complete that event since it's last event (time between iodones), +or, the time to the strategy if the disk had been idle) +.TP +%I/O +percent disk I/O, based on time (DISKTIME) +.TP +load +1 minute load average +.TP +disk_r +total disk read Kb for sample +.TP +disk_w +total disk write Kb for sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +iotop will run forever until Ctrl\-C is hit, or the specified +interval is reached. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iosnoop(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_calldist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_calldist.d.1m new file mode 100644 index 000000000000..d78ce8591b75 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_calldist.d.1m @@ -0,0 +1,48 @@ +.TH j_calldist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_calldist.d - measure Java elapsed times for different types of operation. +.SH SYNOPSIS +.B j_calldist.d +[top] +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). Method calls are only visible when using the +flag "+ExtendedDTraceProbes". eg, java -XX:+ExtendedDTraceProbes classfile + +The "top" optional argument will truncate the output for each report +section to that many lines, with a default of 10. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_calldist.d +.PP +.SH FIELDS +.TP +1 +Process ID +.TP +2 +Type of call (method/gc) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_calldist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_calls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_calls.d.1m new file mode 100644 index 000000000000..e89fb8e53961 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_calls.d.1m @@ -0,0 +1,57 @@ +.TH j_calls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_calls.d - count Java calls (method/...) using DTrace. +.SH SYNOPSIS +.B j_calls.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). Method calls and object allocation are only +visible when using the flag "+ExtendedDTraceProbes". eg, +java -XX:+ExtendedDTraceProbes classfile + +TYPEs: +cload class load +method method call +mcompile method compile +mload compiled method load +oalloc object alloc +thread thread start +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_calls.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (see below) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_calls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_calltime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_calltime.d.1m new file mode 100644 index 000000000000..479dc5bfb48e --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_calltime.d.1m @@ -0,0 +1,51 @@ +.TH j_calltime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_calltime.d - measure Java elapsed times for different types of operation. +.SH SYNOPSIS +.B j_calltime.d +[top] +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). Method calls are only visible when using the +flag "+ExtendedDTraceProbes". eg, java -XX:+ExtendedDTraceProbes classfile + +The "top" optional argument will truncate the output for each report +section to that many lines, with a default of 10. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_calltime.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (method/gc/total) +.TP +NAME +Name of call +.TP +TOTAL +Total elapsed time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_calltime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_classflow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_classflow.d.1m new file mode 100644 index 000000000000..af9d06c1a38b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_classflow.d.1m @@ -0,0 +1,63 @@ +.TH j_classflow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_classflow.d - trace a Java class method flow using DTrace. +.SH SYNOPSIS +.B j_classflow.d +classname +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0) and the flag "+ExtendedDTraceProbes". eg, +java -XX:+ExtendedDTraceProbes classfile + +This watches Java method entries and returns, and indents child +method calls. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_classflow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +PID +Process ID +.TP +CLASS.METHOD +Java class and method name +.SH LEGEND +.TP +\-> +method entry +.TP +<\- +method return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +Changes in TID will appear to shuffle output, as we change from one thread +depth to the next. See Docs/Notes/ALLjavaflow.txt for additional notes. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_classflow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_cpudist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_cpudist.d.1m new file mode 100644 index 000000000000..37fe5f04fc3b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_cpudist.d.1m @@ -0,0 +1,48 @@ +.TH j_cpudist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_cpudist.d - measure Java on-CPU times for different types of operation. +.SH SYNOPSIS +.B j_cpudist.d +[top] +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). Method calls are only visible when using the +flag "+ExtendedDTraceProbes". eg, java -XX:+ExtendedDTraceProbes classfile + +The "top" optional argument will truncate the output for each report +section to that many lines, with a default of 10. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_cpudist.d +.PP +.SH FIELDS +.TP +1 +Process ID +.TP +2 +Type of call (method/gc) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_cpudist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_cputime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_cputime.d.1m new file mode 100644 index 000000000000..a0e767aedccb --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_cputime.d.1m @@ -0,0 +1,51 @@ +.TH j_cputime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_cputime.d - measure Java on-CPU times for different types of operation. +.SH SYNOPSIS +.B j_cputime.d +[top] +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). Method calls are only visible when using the +flag "+ExtendedDTraceProbes". eg, java -XX:+ExtendedDTraceProbes classfile + +The "top" optional argument will truncate the output for each report +section to that many lines, with a default of 10. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_cputime.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (method/gc/total) +.TP +NAME +Name of call +.TP +TOTAL +Total on-CPU time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_cputime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_events.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_events.d.1m new file mode 100644 index 000000000000..6df009b2a7a4 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_events.d.1m @@ -0,0 +1,46 @@ +.TH j_events.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_events.d - count Java events using DTrace. +.SH SYNOPSIS +.B j_events.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). Some events such as method calls are only +visible when using the flag "+ExtendedDTraceProbes". eg, +java -XX:+ExtendedDTraceProbes classfile +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_events.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +EVENT +Event name (DTrace probe name) +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_events.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_flow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_flow.d.1m new file mode 100644 index 000000000000..579e68186c0a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_flow.d.1m @@ -0,0 +1,63 @@ +.TH j_flow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_flow.d - snoop Java execution showing method flow using DTrace. +.SH SYNOPSIS +.B j_flow.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0) and the flag "+ExtendedDTraceProbes". eg, +java -XX:+ExtendedDTraceProbes classfile + +This watches Java method entries and returns, and indents child +method calls. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_flow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +PID +Process ID +.TP +CLASS.METHOD +Java class and method name +.SH LEGEND +.TP +\-> +method entry +.TP +<\- +method return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +Changes in TID will appear to shuffle output, as we change from one thread +depth to the next. See Docs/Notes/ALLjavaflow.txt for additional notes. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_flow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_flowtime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_flowtime.d.1m new file mode 100644 index 000000000000..e4334b23e5b3 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_flowtime.d.1m @@ -0,0 +1,69 @@ +.TH j_flowtime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_flowtime.d - snoop Java execution with method flow and delta times. +.SH SYNOPSIS +.B j_flowtime.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0) and the flag "+ExtendedDTraceProbes". eg, +java -XX:+ExtendedDTraceProbes classfile + +This watches Java method entries and returns, and indents child +method calls. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_flowtime.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +TID +Thread ID +.TP +TIME(us) +Time since boot (us) +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +CLASS.METHOD +Java class and method name +.SH LEGEND +.TP +\-> +method entry +.TP +<\- +method return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +Changes in TID will appear to shuffle output, as we change from one thread +depth to the next. See Docs/Notes/ALLjavaflow.txt for additional notes. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_flowtime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_methodcalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_methodcalls.d.1m new file mode 100644 index 000000000000..a44aea76dbd3 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_methodcalls.d.1m @@ -0,0 +1,45 @@ +.TH j_methodcalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_methodcalls.d - count Java method calls DTrace. +.SH SYNOPSIS +.B j_methodcalls.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0) and the flag "+ExtendedDTraceProbes". eg, +java -XX:+ExtendedDTraceProbes classfile +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_methodcalls.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +COUNT +Number of calls during sample +.TP +CLASS.METHOD +Java class and method name +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_methodcalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_objnew.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_objnew.d.1m new file mode 100644 index 000000000000..14a6b21a0535 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_objnew.d.1m @@ -0,0 +1,45 @@ +.TH j_objnew.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_objnew.d - report Java object allocation using DTrace. +.SH SYNOPSIS +.B j_objnew.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0) and the flag "+ExtendedDTraceProbes". eg, +java -XX:+ExtendedDTraceProbes classfile +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_objnew.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +OBJS +Number of objects created +.TP +CLASS.METHOD +Java class and method name +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_objnew.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_package.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_package.d.1m new file mode 100644 index 000000000000..43f5b9b1623f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_package.d.1m @@ -0,0 +1,44 @@ +.TH j_package.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_package.d - count Java class loads by package using DTrace. +.SH SYNOPSIS +.B j_package.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_package.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +LOADS +Class loads during trace +.TP +PACKAGE +Package name from class +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_package.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_profile.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_profile.d.1m new file mode 100644 index 000000000000..7c1ca28f6b2b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_profile.d.1m @@ -0,0 +1,52 @@ +.TH j_profile.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_profile.d - sample stack traces with Java translations using DTrace. +.SH SYNOPSIS +.SH DESCRIPTION +This samples stack traces for the process specified. This stack trace +will cross the JVM and system libraries, and insert translations for Java +stack frames where appropriate. This is best explained with an example +stack frame output, + +Func_loop.func_c()V +Func_loop.func_b()V +Func_loop.func_a()V +Func_loop.main([Ljava/lang/String;)V +StubRoutines (1) +libjvm.so`__1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHan +libjvm.so`__1cCosUos_exception_wrapper6FpFpnJJavaValue_pnMmetho +libjvm.so`__1cJJavaCallsEcall6FpnJJavaValue_nMmethodHandle_pnRJ +libjvm.so`__1cRjni_invoke_static6FpnHJNIEnv__pnJJavaValue_pnI_j +libjvm.so`jni_CallStaticVoidMethod+0x15d +java`JavaMain+0xd30 +libc.so.1`_thr_setup+0x52 +libc.so.1`_lwp_start +101 + +The lines at the top are Java frames, followed by the JVM (libjvm.so). +The JVM symbols may be translated by passing the output through c++filt. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_profile.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_profile.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_stat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_stat.d.1m new file mode 100644 index 000000000000..ab1495e7b690 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_stat.d.1m @@ -0,0 +1,68 @@ +.TH j_stat.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_stat.d - Java operation stats using DTrace. +.SH SYNOPSIS +.B j_stat.d +[interval [count]] +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). Method calls and object allocation are only +visible when using the flag "+ExtendedDTraceProbes". eg, +java -XX:+ExtendedDTraceProbes classfile + +The numbers are counts for the interval specified. The default interval +is 1 second. + +If you see a count in "EXECS" but not in the other columns, then your +Java software is probably not running with the DTrace hotspot provider. + +If you see counts in "CLOAD" but not in "METHODS", then you Java +software probably isn't running with "+ExtendedDTraceProbes". +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_stat.d +.PP +.SH FIELDS +.TP +EXEC/s +Java programs executed per second, including +those without Java provider support +.TP +METHOD/s +Methods called, per second +.TP +OBJNEW/s +Objects created, per second +.TP +CLOAD/s +Class loads, per second +.TP +EXCP/s +Exceptions raised, per second +.TP +RESC/s +Rescues, per second +.TP +GC/s +Garbage collects, per second +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_stat.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_syscalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_syscalls.d.1m new file mode 100644 index 000000000000..854c9017e59a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_syscalls.d.1m @@ -0,0 +1,48 @@ +.TH j_syscalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_syscalls.d - count Java methods and syscalls using DTrace. +.SH SYNOPSIS +.B j_syscalls.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This traces Java methods if the hotspot provider exists (1.6.0) and +the flag "+ExtendedDTraceProbes" is used. eg, +java -XX:+ExtendedDTraceProbes classfile +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_syscalls.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (method/syscall) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_syscalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_syscolors.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_syscolors.d.1m new file mode 100644 index 000000000000..e6bdebee7d3f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_syscolors.d.1m @@ -0,0 +1,65 @@ +.TH j_syscolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_syscolors.d - trace Java method flow plus syscalls, in color. +.SH SYNOPSIS +.B j_syscolors.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This traces Java methods if the hotspot provider exists (1.6.0) and +the flag "+ExtendedDTraceProbes" is used. eg, +java -XX:+ExtendedDTraceProbes classfile + +This watches Java method entries and returns, and indents child +method calls. + +If the flow appears to jump, check the TID column - the JVM may have +switched to another thread. +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_syscolors.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +TID +Thread ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +TYPE +Type of call (func/syscall) +.TP +NAME +Java method or syscall name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +Changes in TID will appear to shuffle output, as we change from one thread +depth to the next. See Docs/Notes/ALLjavaflow.txt for additional notes. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_syscolors.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_thread.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_thread.d.1m new file mode 100644 index 000000000000..97caf9ffc771 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_thread.d.1m @@ -0,0 +1,54 @@ +.TH j_thread.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_thread.d - snoop Java thread execution using DTrace. +.SH SYNOPSIS +.B j_thread.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_thread.d +.PP +.SH FIELDS +.TP +TIME +Time string +.TP +PID +Process ID +.TP +TID +Thread ID +.TP +THREAD +Thread name +.SH LEGEND +.TP +=> +thread start +.TP +<= +thread end +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_thread.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/j_who.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/j_who.d.1m new file mode 100644 index 000000000000..97d68e8baf5e --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/j_who.d.1m @@ -0,0 +1,51 @@ +.TH j_who.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +j_who.d - trace Java calls by process using DTrace. +.SH SYNOPSIS +.B j_who.d + +.SH DESCRIPTION +This traces activity from all Java processes on the system with hotspot +provider support (1.6.0). + +The argument list is truncated at 55 characters (up to 80 is easily +available). To easily read the full argument list, use other system tools; +on Solaris use "pargs PID". +.SH OS +Solaris +.SH STABILITY +Evolving - uses the DTrace hotspot provider, which may change +as additional features are introduced. Check Java/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B j_who.d +.PP +.SH FIELDS +.TP +PID +Process ID of Java +.TP +UID +User ID of the owner +.TP +CALLS +Number of calls made (a measure of activity) +.TP +ARGS +Process name and arguments +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +j_who.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_calldist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_calldist.d.1m new file mode 100644 index 000000000000..fbd20fcfbb3b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_calldist.d.1m @@ -0,0 +1,46 @@ +.TH js_calldist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_calldist.d - measure JavaScript elapsed times for types of operation. +.SH SYNOPSIS +.B js_calldist.d + +.SH DESCRIPTION +This traces JavaScript activity from all browsers running on the system with +JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_calldist.d +.PP +.SH FIELDS +.TP +1 +Filename of the JavaScript program +.TP +2 +Type of call (func/obj-new) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_calldist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_calls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_calls.d.1m new file mode 100644 index 000000000000..c997293cdd01 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_calls.d.1m @@ -0,0 +1,49 @@ +.TH js_calls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_calls.d - count JavaScript calls using DTrace. +.SH SYNOPSIS +.B js_calls.d + +.SH DESCRIPTION +This traces activity from all browsers on the system that are +running with JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_calls.d +.PP +.SH FIELDS +.TP +FILE +Filename of the JavaScript program +.TP +TYPE +Type of call (func/obj-new/...) +.TP +NAME +Descriptive name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_calls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_calltime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_calltime.d.1m new file mode 100644 index 000000000000..785587b16c10 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_calltime.d.1m @@ -0,0 +1,49 @@ +.TH js_calltime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_calltime.d - measure JavaScript elapsed times for types of operation. +.SH SYNOPSIS +.B js_calltime.d + +.SH DESCRIPTION +This traces JavaScript activity from all browsers running on the system with +JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_calltime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the JavaScript program +.TP +TYPE +Type of call (func/obj-new/gc/total) +.TP +NAME +Name of call +.TP +TOTAL +Total elapsed time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_calltime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_cpudist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_cpudist.d.1m new file mode 100644 index 000000000000..64a9aec98ec8 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_cpudist.d.1m @@ -0,0 +1,46 @@ +.TH js_cpudist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_cpudist.d - measure JavaScript on-CPU times for types of operation. +.SH SYNOPSIS +.B js_cpudist.d + +.SH DESCRIPTION +This traces JavaScript activity from all browsers running on the system with +JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_cpudist.d +.PP +.SH FIELDS +.TP +1 +Filename of the JavaScript program +.TP +2 +Type of call (func/obj-new) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_cpudist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_cputime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_cputime.d.1m new file mode 100644 index 000000000000..2aaefc13c8e1 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_cputime.d.1m @@ -0,0 +1,49 @@ +.TH js_cputime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_cputime.d - measure JavaScript on-CPU times for types of operation. +.SH SYNOPSIS +.B js_cputime.d + +.SH DESCRIPTION +This traces JavaScript activity from all browsers running on the system with +JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_cputime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the JavaScript program +.TP +TYPE +Type of call (func/obj-new/gc/total) +.TP +NAME +Name of call +.TP +TOTAL +Total on-CPU time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_cputime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_execs.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_execs.d.1m new file mode 100644 index 000000000000..61613c040053 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_execs.d.1m @@ -0,0 +1,46 @@ +.TH js_execs.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_execs.d - JavaScript execute snoop using DTrace. +.SH SYNOPSIS +.B js_execs.d + +.SH DESCRIPTION +This traces activity from all browsers on the system that are +running with JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_execs.d +.PP +.SH FIELDS +.TP +TIME +Time of event +.TP +FILE +Filename of the JavaScript program +.TP +LINENO +Line number in filename +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_execs.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_flow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_flow.d.1m new file mode 100644 index 000000000000..5d4ba0d23e7b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_flow.d.1m @@ -0,0 +1,59 @@ +.TH js_flow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_flow.d - snoop JavaScript execution showing function flow using DTrace. +.SH SYNOPSIS +.B js_flow.d + +.SH DESCRIPTION +This traces activity from all browsers on the system that are running +with JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_flow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this function belongs to +.TP +FUNC +Function name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_flow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_flowinfo.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_flowinfo.d.1m new file mode 100644 index 000000000000..1531ce5b428f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_flowinfo.d.1m @@ -0,0 +1,68 @@ +.TH js_flowinfo.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_flowinfo.d - JavaScript function flow with info using DTrace. +.SH SYNOPSIS +.B js_flowinfo.d + +.SH DESCRIPTION +This traces activity from all browsers on the system that are running +with JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_flowinfo.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the JavScript program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (func) +.TP +FUNC +Function name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_flowinfo.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_flowtime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_flowtime.d.1m new file mode 100644 index 000000000000..f90c9998fb70 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_flowtime.d.1m @@ -0,0 +1,62 @@ +.TH js_flowtime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_flowtime.d - JavaScript function flow with delta times using DTrace. +.SH SYNOPSIS +.B js_flowtime.d + +.SH DESCRIPTION +This traces activity from all browsers on the system that are running +with JavaScript provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_flowtime.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this function belongs to +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FUNC +Function name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_flowtime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_objcpu.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_objcpu.d.1m new file mode 100644 index 000000000000..088fa06e70b6 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_objcpu.d.1m @@ -0,0 +1,36 @@ +.TH js_objcpu.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_objcpu.d - measure JavaScript object creation on-CPU time using DTrace. +.SH SYNOPSIS +.B js_objcpu.d + +.SH DESCRIPTION +This traces JavaScript activity from all browsers running on the system +with JavaScript provider support. + +Class names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_objcpu.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_objcpu.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_objgc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_objgc.d.1m new file mode 100644 index 000000000000..691883e6dc6e --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_objgc.d.1m @@ -0,0 +1,60 @@ +.TH js_objgc.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_objgc.d - trace JavaScript Object GC using DTrace. +.SH SYNOPSIS +.B js_objgc.d + +.SH DESCRIPTION +This traces JavaScript activity from all running browers on the system +which support the JavaScript DTrace provider. + +This script provides information on which objects are not being garbage +collected, an issue which causes the browser to steadily leak memory. +We trace object creation (+1) and destruction (-1), and provide a +summary each second of the running tally of the object class and +originating filename. If over the period of several minutes an object +type is still steadily increasing, then that would be of interest. +Be patient, depending on the rate of object creation it can take over +ten minutes for garbage collect to kick in. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_objgc.d +.PP +.SH FIELDS +.TP +FILE +Filename that contained the function +.TP +CLASS +Class to which this new object belongs +.TP +TOTAL +Object entropy (positive == uncollected) +.SH NOTES + +\- it is possible that you will see negative entropy. That happens +when you begin tracing after some objects have already been created, +and then trace their destruction. +\- there are other Things that GC handles, other than Objects; extra +probes can be added to trace them, should the need arise. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_objgc.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_objnew.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_objnew.d.1m new file mode 100644 index 000000000000..83897b5dfbab --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_objnew.d.1m @@ -0,0 +1,46 @@ +.TH js_objnew.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_objnew.d - count JavaScript object creation using DTrace. +.SH SYNOPSIS +.B js_objnew.d + +.SH DESCRIPTION +This traces JavaScript activity from all browsers running on the system +with JavaScript provider support. + +Filename and class names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_objnew.d +.PP +.SH FIELDS +.TP +FILE +Filename of the JavaScript program +.TP +CLASS +Class of new object +.TP +COUNT +Number of object creations during tracing +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_objnew.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_stat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_stat.d.1m new file mode 100644 index 000000000000..3234630a3022 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_stat.d.1m @@ -0,0 +1,52 @@ +.TH js_stat.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_stat.d - JavaScript operation stats using DTrace. +.SH SYNOPSIS +.B js_stat.d +[interval [count]] +.SH DESCRIPTION +This traces activity from all browsers on the system that are +running with JavaScript provider support. + +The numbers are counts for the interval specified. The default interval +is 1 second. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_stat.d +.PP +.SH FIELDS +.TP +EXEC/s +JavaScript programs executed per second +.TP +FUNCS/s +Functions called, per second +.TP +OBJNEW/s +Objects created, per second +.TP +OBJFRE/s +Objects freed (finalize), per second +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_stat.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/js_who.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/js_who.d.1m new file mode 100644 index 000000000000..119ea2626bd3 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/js_who.d.1m @@ -0,0 +1,49 @@ +.TH js_who.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +js_who.d - trace JavaScript function execution by process using DTrace. +.SH SYNOPSIS +.B js_who.d + +.SH DESCRIPTION +This traces JavaScript activity from all browsers on the system that are +running with JavaScript provider support. + +Filenames are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace JavaScript provider, which may change +as additional features are introduced. Check JavaScript/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B js_who.d +.PP +.SH FIELDS +.TP +PID +Process ID of JavaScript +.TP +UID +User ID of the owner +.TP +FUNCS +Number of function calls +.TP +FILE +Pathname of the JavaScript program +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +js_who.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/kill.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/kill.d.1m new file mode 100644 index 000000000000..e9e966a9c92b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/kill.d.1m @@ -0,0 +1,53 @@ +.TH kill.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +kill.d \- snoop process signals as they occur. Uses DTrace. +.SH SYNOPSIS +.B kill.d +.SH DESCRIPTION +kill.d is a simple DTrace program to print details of process +signals as they are sent, such as the PID source and destination, +signal number and result. + +This program can be used to determine which process is sending +signals to which other process. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +Default output, print process signals as they are sent. +# +.B kill.d +.PP +.SH FIELDS +.TP +FROM +source PID +.TP +COMMAND +source command name +.TP +TO +destination PID +.TP +SIG +destination signal ("9" for a kill -9) +.TP +RESULT +result of signal (-1 is for failure) +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +kill.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/kstat_types.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/kstat_types.d.1m new file mode 100644 index 000000000000..8a2d11952c45 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/kstat_types.d.1m @@ -0,0 +1,50 @@ +.TH kstat_types.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +kstat_types.d \- Trace kstat reads with type info. Uses DTrace. +.SH SYNOPSIS +.B kstat_types.d +.SH DESCRIPTION +kstat is the Kernel Statistics framework, which is used by tools +such as vmstat, iostat, mpstat and sar. Try running vmstat while +kstat_types.d is tracing - you should see details of the kstat +reads performed. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Trace kstat reads as they occur, +# +.B kstat_types.d +.PP +.SH FIELDS +.TP +CMD +command name +.TP +CLASS +kstat class (ks_class) +.TP +TYPE +kstat type as a string (ks_type) +.TP +MOD:INS:NAME +kstat module:instance:name +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +kstat_types.d will trace until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), kstat(1M), kstat(3KSTAT) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/lastwords.1m b/cddl/contrib/dtracetoolkit/Man/man1m/lastwords.1m new file mode 100644 index 000000000000..024234bf49f7 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/lastwords.1m @@ -0,0 +1,56 @@ +.TH lastwords 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +lastwords \- print syscalls before exit. Uses DTrace. +.SH SYNOPSIS +.B lastwords command +.SH DESCRIPTION +This prints the last few system calls for processes matching +the given name, when they exit. This makes use of a ring buffer +so that the impact on the system is minimised. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall and proc providers. +.SH EXAMPLES +.TP +Catch last few syscalls for dying netscape processes, +# +.B lastwords netscape +.PP +.SH FIELDS +.TP +TIME +time of syscall return, ns +.TP +PID +process ID +.TP +EXEC +process name (execname) +.TP +SYSCALL +system call +.TP +RETURN +return value for the system call +.TP +ERR +errno for the system call +.PP +.SH BASED ON +/usr/demo/dtrace/ring.d +.PP +.SH DOCUMENTATION +DTrace Guide "Buffers and Buffering" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +lastwords will sample until a command with that name exits. +.SH SEE ALSO +dtruss(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/loads.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/loads.d.1m new file mode 100644 index 000000000000..f18d3b119507 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/loads.d.1m @@ -0,0 +1,38 @@ +.TH loads.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +loads.d \- print load averages. Uses DTrace. +.SH SYNOPSIS +.B loads.d +.SH DESCRIPTION +These are the same load averages that the "uptime" command prints. +The purpose of this script is to demonstrate fetching these values +from the DTrace language. + +The first field is the 1 minute average, the second is the 5 minute, +and the third is the 15 minute average. The value represents the average +number of runnable threads in the system, a value higher than your +CPU (core/hwthread) count may be a sign of CPU saturation. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - uses kernel symbols, which may change for a future version +of this OS. +.SH EXAMPLES +.TP +Print load averages, +# +.B loads.d +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +uptime(1), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/lockbydist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/lockbydist.d.1m new file mode 100644 index 000000000000..188c5a4e5f40 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/lockbydist.d.1m @@ -0,0 +1,54 @@ +.TH lockbydist.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +lockbydist.d \- lock distrib. by process name. Uses DTrace. +.SH SYNOPSIS +.B lockbydist.d +.SH DESCRIPTION +lockbydist.d is a DTrace OneLiner to a report the time threads have +spent blocked on adaptive mutexes, by process name. + +A distribution is printed to illustrate the number of blocks at +different lengths in time. This helps us identify if there are many +short blocks, or fewer large blocks. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the lockstat provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B lockbydist.d +.PP +.SH FIELDS +.TP +process name +The process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +value +The blocked time in nanoseconds +.TP +count +The number of occurrences that were at least this size +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +lockbydist.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +lockstat(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/lockbyproc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/lockbyproc.d.1m new file mode 100644 index 000000000000..af6c9114b71a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/lockbyproc.d.1m @@ -0,0 +1,47 @@ +.TH lockbyproc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +lockbyproc.d \- lock time by process name. Uses DTrace. +.SH SYNOPSIS +.B lockbyproc.d +.SH DESCRIPTION +lockbyproc.d is a DTrace OneLiner to a report the total time threads +have spent blocked on adaptive mutexes, by process name. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the lockstat provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B lockbyproc.d +.PP +.SH FIELDS +.TP +first field +This is the process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +second field +This is the total length of time blocked, in nanoseconds. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +lockbyproc.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +lockstat(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/minfbypid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/minfbypid.d.1m new file mode 100644 index 000000000000..45574f487ae0 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/minfbypid.d.1m @@ -0,0 +1,46 @@ +.TH minfbypid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +minfbypid.d \- minor faults by process name. Uses DTrace. +.SH SYNOPSIS +.B minfbypid.d +.SH DESCRIPTION +minfbypid.d is a DTrace OneLiner to a report the number of minor +faults by process name. + +This is based on a script from DExplorer. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the vminfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B minfbypid.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +MINFAULTS +number of minor faults in this sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +minfbypid.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/minfbyproc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/minfbyproc.d.1m new file mode 100644 index 000000000000..9045e48da762 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/minfbyproc.d.1m @@ -0,0 +1,47 @@ +.TH minfbyproc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +minfbyproc.d \- minor faults by process name. Uses DTrace. +.SH SYNOPSIS +.B minfbyproc.d +.SH DESCRIPTION +minfbyproc.d is a DTrace OneLiner to a report the number of minor +faults by process name. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the vminfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B minfbyproc.d +.PP +.SH FIELDS +.TP +first field +The process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +second field +The number minor faults +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +minfbyproc.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/mmapfiles.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/mmapfiles.d.1m new file mode 100644 index 000000000000..e4bb2c89eaef --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/mmapfiles.d.1m @@ -0,0 +1,42 @@ +.TH mmapfiles.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +mmapfiles.d \- mmap'd files by process. Uses DTrace. +.SH SYNOPSIS +.B mmapfiles.d +.SH DESCRIPTION +This prints statistics on the pathnames that were mmap'd by processes. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B mmapfiles.d +.PP +.SH FIELDS +.TP +MMAPS +number of mmaps +.TP +CMD +process name +.TP +PATHNAME +pathname of mmap'd file +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +mmapfiles.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/modcalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/modcalls.d.1m new file mode 100644 index 000000000000..af7722b71c4c --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/modcalls.d.1m @@ -0,0 +1,50 @@ +.TH modcalls.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +modcalls.d \- kernel function calls by module. Uses DTrace. +.SH SYNOPSIS +.B modcalls.d +.SH DESCRIPTION +modcalls.d is a DTrace OneLiner to a report of the number of +kernel function calls by module. + +This script may be useful to determine whether drivers are "thinking" when +troubleshooting driver issues. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Any +.SH STABILITY +stable - while this script uses the unstable fbt provider, it does so +in a stable way. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B modcalls.d +.PP +.SH FIELDS +.TP +first field +This is the module name, or kernel driver name. if a name is +unfamiliar to you there may be a man page to explain what it is. +.TP +second field +This is the number of function calls by this module. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +modcalls.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/newproc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/newproc.d.1m new file mode 100644 index 000000000000..b3b979b4e779 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/newproc.d.1m @@ -0,0 +1,54 @@ +.TH newproc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +newproc.d \- snoop new processes. Uses DTrace. +.SH SYNOPSIS +.B newproc.d +.SH DESCRIPTION +newproc.d is a DTrace OneLiner to snoop new processes as they are run. +The argument listing is printed. + +This is useful to identify short lived processes that are usually +difficult to spot using traditional tools. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the proc provider. +.SH EXAMPLES +.TP +This prints new processes until Ctrl\-C is hit. +# +.B newproc.d +.PP +.SH FIELDS +.TP +CPU +The CPU that recieved the event +.TP +ID +A DTrace probe ID for the event +.TP +FUNCTION:NAME +The DTrace probe name for the event +.TP +remaining fields +These contains the argument listing for the new process +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +newproc.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +execsnoop(1M), dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/nfswizard.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/nfswizard.d.1m new file mode 100644 index 000000000000..64d8e416e83f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/nfswizard.d.1m @@ -0,0 +1,36 @@ +.TH nfswizard.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +nfswizard.d \- nfs client activity wizard. Uses DTrace. +.SH SYNOPSIS +.B nfswizard.d +.SH DESCRIPTION +This examines activity caused by NFS client processes on the same server +that you are running this script on. A detailed report is generated +to explain various details of NFS client activity, including response +times and file access. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.PP +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH EXAMPLES +.TP +Sample NFS client activity, then print a report after Ctrl\-C, +# +.B nfswizard.d +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +nfswizard.d will sample activity until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/opensnoop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/opensnoop.1m new file mode 100644 index 000000000000..bc449c05b1b9 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/opensnoop.1m @@ -0,0 +1,139 @@ +.TH opensnoop 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +opensnoop \- snoop file opens as they occur. Uses DTrace. +.SH SYNOPSIS +.B opensnoop +[\-a|\-A|\-ceghsvxZ] [\-f pathname] [\-n name] [\-p PID] +.SH DESCRIPTION +opensnoop tracks file opens. As a process issues a file open, details +such as UID, PID and pathname are printed out. + +The returned file descriptor is printed, +a value of -1 indicates an error. This can be useful +for troubleshooting to determine if appliacions are attempting to +open files that do not exist. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH OPTIONS +.TP +\-a +print all data +.TP +\-A +dump all data, space delimited +.TP +\-c +print current working directory of process +.TP +\-e +print errno value +.TP +\-g +print full command arguments +.TP +\-s +print start time, us +.TP +\-v +print start time, string +.TP +\-x +only print failed opens +.TP +\-Z +print zonename +.TP +\-f pathname +file pathname to snoop +.TP +\-n name +process name to snoop +.TP +\-p PID +process ID to snoop +.PP +.SH EXAMPLES +.TP +Default output, print file opens by process as they occur, +# +.B opensnoop +.PP +.TP +Print human readable timestamps, +# +.B opensnoop +\-v +.PP +.TP +See error codes, +# +.B opensnoop +\-e +.PP +.TP +Snoop this file only, +# +.B opensnoop +\-f /etc/passwd +.PP +.SH FIELDS +.TP +ZONE +Zone name +.TP +UID +User ID +.TP +PID +Process ID +.TP +PPID +Parent Process ID +.TP +FD +File Descriptor (-1 is error) +.TP +ERR +errno value (see /usr/include/sys/errno.h) +.TP +CWD +current working directory of process +.TP +PATH +pathname for file open +.TP +COMM +command name for the process +.TP +ARGS +argument listing for the process +.TP +TIME +timestamp for the open event, us +.TP +STRTIME +timestamp for the open event, string +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +opensnoop will run forever until Ctrl\-C is hit. +.SH BUGS +occasionally the pathname for the file open cannot be read +and the following error will be seen, + +dtrace: error on enabled probe ID 6 (...): invalid address + +this is normal behaviour. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pathopens.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pathopens.d.1m new file mode 100644 index 000000000000..cf043bd1c3f6 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pathopens.d.1m @@ -0,0 +1,38 @@ +.TH pathopens.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +pathopens.d \- full pathnames opened ok count. Uses DTrace. +.SH SYNOPSIS +.B pathopens.d +.SH DESCRIPTION +This program prints a count of the number of times files have been +successfully opened. This is somewhat special in that the full pathname +is calculated, even if the file open referred to a relative pathname. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B pathopens.d +.PP +.SH FIELDS +.TP +PATHNAME +full pathname +.TP +COUNT +number of successful opens +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +pathopens.d will sample until Ctrl\-C is hit. +.SH SEE ALSO +opensnoop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pfilestat.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pfilestat.1m new file mode 100644 index 000000000000..8780c2e58e1c --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pfilestat.1m @@ -0,0 +1,87 @@ +.TH pfilestat 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +pfilestat \- show I/O latency break down by FD. Uses DTrace. +.SH SYNOPSIS +.B pfilestat [\-r|\-w] pid +.SH DESCRIPTION +This prints I/O statistics for each file descriptor within a process. +In particular, the time break down during read() and write() events is +measured. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH OPTIONS +.TP +\-r +reads only +.TP +\-w +writes only +.TP +pid +process ID to examine +.PP +.SH EXAMPLES +.TP +Sample both read and write activity for PID 81, +# +.B pfilestat 81 +.TP +Sample reads only for PID 81, +# +.B pfilestat +\-r 81 +.PP +.SH FIELDS +.TP +STATE +microstate. see STATES below. +.TP +FDUM +file Descriptor ID +.TP +Time +percentage of wallclock time in each STATE +.TP +File +Name of file, if known +.PP +.SH STATES +.TP +read +Time spent during the execution of the read() syscall. +.TP +write +Time spent during the execution of the write() syscall. +.TP +waitcpu +Latency spent waiting to be scheduled after becoming runnable. +.TP +running +Process running user-mode code. +.TP +sleep-r +Process sleeping on reads. +.TP +sleep-w +Process sleeping on writes. +.PP +.SH DOCUMENTATION +pfilestat is discussed and demonstrated in Solaris Internals 2nd edition, +volume 2. + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +pfilestat will sample until Ctrl\-C is hit. +.SH AUTHOR +Richard McDougall +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pgpginbypid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pgpginbypid.d.1m new file mode 100644 index 000000000000..fdaa297b51d0 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pgpginbypid.d.1m @@ -0,0 +1,47 @@ +.TH pgpginbypid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +pgpginbypid.d \- pages paged in by PID. Uses DTrace. +.SH SYNOPSIS +.B pgpginbypid.d +.SH DESCRIPTION +pgpginbypid.d reports the rumber of pages paged in from the disks +by process ID. This is an indicator that processes are reading +from the disks. + +This is based on a script from DExplorer. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the vminfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B pgpginbypid.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +PAGES +number of pages paged in +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +pgpginbypid.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iosnoop(1m), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pgpginbyproc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pgpginbyproc.d.1m new file mode 100644 index 000000000000..413043af10e5 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pgpginbyproc.d.1m @@ -0,0 +1,50 @@ +.TH pgpginbyproc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +pgpginbyproc.d \- pages pagedin by process name. Uses DTrace. +.SH SYNOPSIS +.B pgpginbyproc.d +.SH DESCRIPTION +pgpginbyproc.d is a DTrace OneLiner to a report the number of pages +paged in by process name. + +This may be one way to help identify the process responsible for +causing heavy read traffic to the disks. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the vminfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B pgpginbyproc.d +.PP +.SH FIELDS +.TP +first field +The process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +second field +The number of pages paged in +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +pgpginbyproc.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iosnoop(1m), dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_calldist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_calldist.d.1m new file mode 100644 index 000000000000..065d6db2d7d1 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_calldist.d.1m @@ -0,0 +1,49 @@ +.TH php_calldist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_calldist.d - measure PHP elapsed times for functions. +.SH SYNOPSIS +.B php_calldist.d + +.SH DESCRIPTION +This traces PHP activity from all programs running on the system with +PHP provider support. + +This script prints distribution plots of elapsed time for PHP +operations. Use php_calltime.d for summary reports. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_calldist.d +.PP +.SH FIELDS +.TP +1 +Filename of the PHP program +.TP +2 +Type of call (func) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_calldist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_calltime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_calltime.d.1m new file mode 100644 index 000000000000..f090b6e70160 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_calltime.d.1m @@ -0,0 +1,49 @@ +.TH php_calltime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_calltime.d - measure PHP elapsed times for functions. +.SH SYNOPSIS +.B php_calltime.d + +.SH DESCRIPTION +This traces PHP activity from all programs running on the system with +PHP provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_calltime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the PHP program +.TP +TYPE +Type of call (func/total) +.TP +NAME +Name of call +.TP +TOTAL +Total elapsed time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_calltime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_cpudist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_cpudist.d.1m new file mode 100644 index 000000000000..54ea0d195b84 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_cpudist.d.1m @@ -0,0 +1,49 @@ +.TH php_cpudist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_cpudist.d - measure PHP on-CPU times for functions. +.SH SYNOPSIS +.B php_cpudist.d + +.SH DESCRIPTION +This traces PHP activity from all programs running on the system with +PHP provider support. + +This script prints distribution plots of elapsed time for PHP +operations. Use php_cputime.d for summary reports. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_cpudist.d +.PP +.SH FIELDS +.TP +1 +Filename of the PHP program +.TP +2 +Type of call (func) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_cpudist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_cputime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_cputime.d.1m new file mode 100644 index 000000000000..2020969224f6 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_cputime.d.1m @@ -0,0 +1,49 @@ +.TH php_cputime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_cputime.d - measure PHP on-CPU times for functions. +.SH SYNOPSIS +.B php_cputime.d + +.SH DESCRIPTION +This traces PHP activity from all programs running on the system with +PHP provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_cputime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the PHP program +.TP +TYPE +Type of call (func/total) +.TP +NAME +Name of call (function name) +.TP +TOTAL +Total on-CPU time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_cputime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_flow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_flow.d.1m new file mode 100644 index 000000000000..bda09e3b24d6 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_flow.d.1m @@ -0,0 +1,60 @@ +.TH php_flow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_flow.d - snoop PHP execution showing function flow. +.SH SYNOPSIS +.B php_flow.d + +.SH DESCRIPTION +This traces PHP activity from all PHP programs on the system +running with PHP provider support. + +This watches PHP function entries and returns, and indents child +function calls. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_flow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this function belongs to +.TP +FUNC +Function name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_flow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_flowinfo.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_flowinfo.d.1m new file mode 100644 index 000000000000..2e9282e73035 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_flowinfo.d.1m @@ -0,0 +1,68 @@ +.TH php_flowinfo.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_flowinfo.d - snoop PHP function flow with info using DTrace. +.SH SYNOPSIS +.B php_flowinfo.d + +.SH DESCRIPTION +This traces activity from all PHP programs on the system that are +running with PHP provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_flowinfo.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the PHP program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (func) +.TP +FUNC +PHP function +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_flowinfo.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_flowtime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_flowtime.d.1m new file mode 100644 index 000000000000..f30c283e5476 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_flowtime.d.1m @@ -0,0 +1,65 @@ +.TH php_flowtime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_flowtime.d - snoop PHP functions with flow and delta times. +.SH SYNOPSIS +.B php_flowtime.d + +.SH DESCRIPTION +This traces shell activity from PHP programs on the system that are +running with PHP provider support. + +This watches PHP function entries and returns, and indents child +function calls. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_flowtime.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this function belongs to +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FUNC +PHP function name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_flowtime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_funccalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_funccalls.d.1m new file mode 100644 index 000000000000..eb01963bb2fa --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_funccalls.d.1m @@ -0,0 +1,43 @@ +.TH php_funccalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_funccalls.d - measure PHP function calls using DTrace. +.SH SYNOPSIS +.B php_funccalls.d + +.SH DESCRIPTION +This traces PHP activity from all running programs on the system +which support the PHP DTrace provider. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_funccalls.d +.PP +.SH FIELDS +.TP +FUNC +PHP function name +.TP +CALLS +Function calls during this sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_funccalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_malloc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_malloc.d.1m new file mode 100644 index 000000000000..a11944d9537c --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_malloc.d.1m @@ -0,0 +1,39 @@ +.TH php_malloc.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_malloc.d - PHP libc malloc analysis. +.SH SYNOPSIS +.B php_malloc.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This is an expiremental script to identify who is calling malloc() for +memory allocation, and to print distribution plots of the requested bytes. +If a malloc() occured while in a PHP function, then that function is +identified as responsible; else the caller of malloc() is identified as +responsible - which will be a function from the PHP engine. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_malloc.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_malloc.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_syscalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_syscalls.d.1m new file mode 100644 index 000000000000..e2b10b0f84fa --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_syscalls.d.1m @@ -0,0 +1,54 @@ +.TH php_syscalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_syscalls.d - count PHP function calls and syscalls using DTrace. +.SH SYNOPSIS +.B php_syscalls.d + +.SH DESCRIPTION +This traces syscalls that occured during a PHP function call. + +Filename and function names are printed if available. +The filename for syscalls may be printed as "php", if the program +was invoked using the form "php filename" rather than running the +program with an interpreter line. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_syscalls.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +FILE +Filename of the PHP program +.TP +TYPE +Type of call (func/syscall) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_syscalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_syscolors.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_syscolors.d.1m new file mode 100644 index 000000000000..0a29ffb43913 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_syscolors.d.1m @@ -0,0 +1,61 @@ +.TH php_syscolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_syscolors.d - trace PHP function flow plus syscalls, in color. +.SH SYNOPSIS +.B php_syscolors.d + +.SH DESCRIPTION +This watches PHP function entries and returns, and indents child +function calls. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_syscolors.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the PHP program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (func/syscall) +.TP +NAME +PHP function or syscall name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_syscolors.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/php_who.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/php_who.d.1m new file mode 100644 index 000000000000..9aacba6221ef --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/php_who.d.1m @@ -0,0 +1,49 @@ +.TH php_who.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +php_who.d - trace PHP function execution by process using DTrace. +.SH SYNOPSIS +.B php_who.d + +.SH DESCRIPTION +This traces PHP activity from all PHP programs on the system that are +running with PHP provider support. + +Filenames are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Php provider, which may change +as additional features are introduced. Check Php/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B php_who.d +.PP +.SH FIELDS +.TP +PID +Process ID of PHP +.TP +UID +User ID of the owner +.TP +FUNCS +Number of function calls +.TP +FILE +Pathname of the PHP program +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +php_who.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pidpersec.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pidpersec.d.1m new file mode 100644 index 000000000000..4040ae549f26 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pidpersec.d.1m @@ -0,0 +1,42 @@ +.TH pidpersec.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +pidpersec.d \- print new PIDs per sec. Uses DTrace. +.SH SYNOPSIS +.B pidpersec.d +.SH DESCRIPTION +This script prints the number of new processes created per second. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the proc provider. +.SH EXAMPLES +.TP +Print PID statistics per second, +# +.B pidpersec.d +.PP +.SH FIELDS +.TP +TIME +time, as a string +.TP +LASTPID +last PID created +.TP +PID/s +Number of processes created per second +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +pidpersec.d will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +execsnoop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_calldist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_calldist.d.1m new file mode 100644 index 000000000000..ad2d1b83d184 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_calldist.d.1m @@ -0,0 +1,49 @@ +.TH pl_calldist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_calldist.d - measure Perl elapsed times for subroutines. +.SH SYNOPSIS +.B pl_calldist.d + +.SH DESCRIPTION +This traces Perl activity from all programs running on the system with +Perl provider support. + +This script prints distribution plots of elapsed time for Perl subroutines. +Use pl_calltime.d for summary reports. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_calldist.d +.PP +.SH FIELDS +.TP +1 +Filename of the Perl program +.TP +2 +Type of call (sub) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_calldist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_calltime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_calltime.d.1m new file mode 100644 index 000000000000..7de6eaf7a7c1 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_calltime.d.1m @@ -0,0 +1,49 @@ +.TH pl_calltime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_calltime.d - measure Perl elapsed times for subroutines. +.SH SYNOPSIS +.B pl_calltime.d + +.SH DESCRIPTION +This traces Perl activity from all programs running on the system with +Perl provider support. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_calltime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Perl program +.TP +TYPE +Type of call (sub/total) +.TP +NAME +Name of call +.TP +TOTAL +Total elapsed time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_calltime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_cpudist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_cpudist.d.1m new file mode 100644 index 000000000000..6df61f1bb4de --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_cpudist.d.1m @@ -0,0 +1,49 @@ +.TH pl_cpudist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_cpudist.d - measure Perl on-CPU times for subroutines. +.SH SYNOPSIS +.B pl_cpudist.d + +.SH DESCRIPTION +This traces Perl activity from all programs running on the system with +Perl provider support. + +This script prints distribution plots of elapsed time for Perl subrotines. +Use pl_cputime.d for summary reports. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_cpudist.d +.PP +.SH FIELDS +.TP +1 +Filename of the Perl program +.TP +2 +Type of call (sub) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_cpudist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_cputime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_cputime.d.1m new file mode 100644 index 000000000000..f8cf75aed423 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_cputime.d.1m @@ -0,0 +1,49 @@ +.TH pl_cputime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_cputime.d - measure Perl on-CPU times for subroutines. +.SH SYNOPSIS +.B pl_cputime.d + +.SH DESCRIPTION +This traces Perl activity from all programs running on the system with +Perl provider support. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_cputime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Perl program +.TP +TYPE +Type of call (sub/total) +.TP +NAME +Name of call (subroutine name) +.TP +TOTAL +Total on-CPU time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_cputime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_flow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_flow.d.1m new file mode 100644 index 000000000000..d66e49363069 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_flow.d.1m @@ -0,0 +1,60 @@ +.TH pl_flow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_flow.d - snoop Perl execution showing subroutine flow. +.SH SYNOPSIS +.B pl_flow.d + +.SH DESCRIPTION +This traces Perl activity from all Perl programs on the system +running with Perl provider support. + +This watches Perl subroutine entries and returns, and indents child +subroutine calls. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_flow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this subroutine belongs to +.TP +SUB +Subroutine name +.SH LEGEND +.TP +\-> +subroutine entry +.TP +<\- +subroutine return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_flow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_flowinfo.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_flowinfo.d.1m new file mode 100644 index 000000000000..0bf1384bfdbf --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_flowinfo.d.1m @@ -0,0 +1,68 @@ +.TH pl_flowinfo.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_flowinfo.d - snoop Perl subroutine flow with info using DTrace. +.SH SYNOPSIS +.B pl_flowinfo.d + +.SH DESCRIPTION +This traces activity from all Perl programs on the system that are +running with Perl provider support. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_flowinfo.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the Perl program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (sub) +.TP +SUB +Perl subroutine +.SH LEGEND +.TP +\-> +subroutine entry +.TP +<\- +subroutine return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_flowinfo.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_flowtime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_flowtime.d.1m new file mode 100644 index 000000000000..59acddf363ed --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_flowtime.d.1m @@ -0,0 +1,65 @@ +.TH pl_flowtime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_flowtime.d - snoop Perl subroutines with flow and delta times. +.SH SYNOPSIS +.B pl_flowtime.d + +.SH DESCRIPTION +This traces shell activity from Perl programs on the system that are +running with Perl provider support. + +This watches Perl subroutine entries and returns, and indents child +subroutine calls. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_flowtime.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this subroutine belongs to +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +SUB +Perl subroutine name +.SH LEGEND +.TP +\-> +method entry +.TP +<\- +method return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_flowtime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_malloc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_malloc.d.1m new file mode 100644 index 000000000000..babee557d35d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_malloc.d.1m @@ -0,0 +1,39 @@ +.TH pl_malloc.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_malloc.d - Perl libc malloc analysis. +.SH SYNOPSIS +.B pl_malloc.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This is an expiremental script to identify who is calling malloc() for +memory allocation, and to print distribution plots of the requested bytes. +If a malloc() occured while in a Perl subroutine, then that subroutine is +identified as responsible; else the caller of malloc() is identified as +responsible - which will be a function from the Perl engine. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_malloc.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_malloc.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_subcalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_subcalls.d.1m new file mode 100644 index 000000000000..710b39dde66d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_subcalls.d.1m @@ -0,0 +1,43 @@ +.TH pl_subcalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_subcalls.d - measure Perl subroutine calls using DTrace. +.SH SYNOPSIS +.B pl_subcalls.d + +.SH DESCRIPTION +This traces Perl activity from all running programs on the system +which support the Perl DTrace provider. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_subcalls.d +.PP +.SH FIELDS +.TP +SUB +Perl subroutine name +.TP +CALLS +Subroutine calls during this sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_subcalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_syscalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_syscalls.d.1m new file mode 100644 index 000000000000..bd35e5c685bc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_syscalls.d.1m @@ -0,0 +1,49 @@ +.TH pl_syscalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_syscalls.d - count Perl subroutine calls and syscalls using DTrace. +.SH SYNOPSIS +.B pl_syscalls.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +Filename and subroutine names are printed if available. +The filename for syscalls may be printed as "perl", if the program +was invoked using the form "perl filename" rather than running the +program with an interpreter line. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_syscalls.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Perl program +.TP +TYPE +Type of call (sub/syscall) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_syscalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_syscolors.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_syscolors.d.1m new file mode 100644 index 000000000000..5c4c4bac1dbe --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_syscolors.d.1m @@ -0,0 +1,61 @@ +.TH pl_syscolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_syscolors.d - trace Perl subroutine flow plus syscalls, in color. +.SH SYNOPSIS +.B pl_syscolors.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This watches Perl subroutine entries and returns, and indents child +subroutine calls. + +Filename and subroutine names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_syscolors.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the Perl program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (sub/syscall) +.TP +NAME +Perl subroutine or syscall name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_syscolors.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pl_who.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pl_who.d.1m new file mode 100644 index 000000000000..9239a7023849 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pl_who.d.1m @@ -0,0 +1,49 @@ +.TH pl_who.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +pl_who.d - trace Perl subroutine execution by process using DTrace. +.SH SYNOPSIS +.B pl_who.d + +.SH DESCRIPTION +This traces Perl activity from all Perl programs on the system that are +running with Perl provider support. + +Filenames are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Perl provider, which may change +as additional features are introduced. Check Perl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B pl_who.d +.PP +.SH FIELDS +.TP +PID +Process ID of Perl +.TP +UID +User ID of the owner +.TP +SUBS +Number of subroutine calls +.TP +FILE +Pathname of the Perl program +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +pl_who.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/priclass.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/priclass.d.1m new file mode 100644 index 000000000000..d726ac2588f1 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/priclass.d.1m @@ -0,0 +1,66 @@ +.TH priclass.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +priclass.d \- priority distribution by scheduling class. Uses DTrace. +.SH SYNOPSIS +.B priclass.d +.SH DESCRIPTION +This is a simple DTrace script that samples at 1000 Hz the current +thread's scheduling class and priority. A distribution plot is printed. + +With priorities, the higher the priority the better chance the thread +has of being scheduled. + +This idea came from the script /usr/demo/dtrace/pri.d, which +produces similar output for priority changes, not samples. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B priclass.d +.PP +.SH FIELDS +.TP +value +process priority +.TP +count +number of samples of at least this priority +.PP +.SH SCHEDULING CLASSES +.TP +TS +time sharing +.TP +IA +interactive +.TP +RT +real time +.TP +SYS +system +.TP +FSS +fair share scheduler +.PP +.SH BASED ON +/usr/demo/dtrace/pri.d +.PP +.SH DOCUMENTATION +DTrace Guide "profile Provider" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +priclass.d will sample until Ctrl\-C is hit. +.SH SEE ALSO +pridist.d(1M), dispadmin(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/pridist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/pridist.d.1m new file mode 100644 index 000000000000..1e7aba625442 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/pridist.d.1m @@ -0,0 +1,55 @@ +.TH pridist.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +pridist.d \- process priority distribution. Uses DTrace. +.SH SYNOPSIS +.B pridist.d +.SH DESCRIPTION +This is a simple DTrace script that samples at 1000 Hz which process +is on the CPUs, and what the priority is. A distribution plot is printed. + +With priorities, the higher the priority the better chance the process +(actually, thread) has of being scheduled. + +This idea came from the script /usr/demo/dtrace/profpri.d, which +produces similar output for one particular PID. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B pridist.d +.PP +.SH FIELDS +.TP +CMD +process name +.TP +PID +process ID +.TP +value +process priority +.TP +count +number of samples of at least this priority +.PP +.SH BASED ON +/usr/demo/dtrace/profpri.d +.PP +.SH DOCUMENTATION +DTrace Guide "profile Provider" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +pridist.d will sample until Ctrl\-C is hit. +.SH SEE ALSO +dispadmin(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/procsystime.1m b/cddl/contrib/dtracetoolkit/Man/man1m/procsystime.1m new file mode 100644 index 000000000000..0df87cf78832 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/procsystime.1m @@ -0,0 +1,108 @@ +.TH procsystime 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +procsystime \- analyse system call times. Uses DTrace. +.SH SYNOPSIS +.B procsystime +[\-acehoT] [ -p PID | -n name | command ] +.SH DESCRIPTION +procsystime prints details on system call times for processes, +both the elapsed times and on-cpu times can be printed. + +The elapsed times are interesting, to help identify syscalls +that take some time to complete (during which the process may +have slept). CPU time helps us identify syscalls that +are consuming CPU cycles to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH OPTIONS +.TP +\-a +print all data +.TP +\-c +print syscall counts +.TP +\-e +print elapsed times, ns +.TP +\-o +print CPU times, ns +.TP +\-T +print totals +.TP +\-p PID +examine this PID +.TP +\-n name +examine processes which have this name +.SH EXAMPLES +.TP +Print elapsed times for PID 1871, +# +.B procsystime +\-p 1871 +.PP +.TP +Print elapsed times for processes called "tar", +# +.B procsystime +\-n tar +.PP +.TP +Print CPU times for "tar" processes, +# +.B procsystime +\-on tar +.PP +.TP +Print syscall counts for "tar" processes, +# +.B procsystime +\-cn tar +.PP +.TP +Print elapsed and CPU times for "tar" processes, +# +.B procsystime +\-eon tar +.PP +.TP +print all details for "bash" processes, +# +.B procsystime +\-aTn bash +.PP +.TP +run and print details for "df -h", +# +.B procsystime +df \-h +.PP +.SH FIELDS +.TP +SYSCALL +System call name +.TP +TIME (ns) +Total time, nanoseconds +.TP +COUNT +Number of occurrences +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +procsystime will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtruss(1M), dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/putnexts.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/putnexts.d.1m new file mode 100644 index 000000000000..59335673299d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/putnexts.d.1m @@ -0,0 +1,27 @@ +.TH putnexts.d 1m "$Date:: 2007-09-12 #$" "USER COMMANDS" +.SH NAME +putnexts.d - +.SH SYNOPSIS +.SH DESCRIPTION + +.SH OS +Solaris +.SH STABILITY +stable - +.SH EXAMPLES +.TP +Default output, +# +.B putnexts.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +putnexts.d will run until Ctrl-C is hit. +.SH AUTHOR + +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_calldist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_calldist.d.1m new file mode 100644 index 000000000000..1592af5e8223 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_calldist.d.1m @@ -0,0 +1,49 @@ +.TH py_calldist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_calldist.d - measure Python elapsed times for functions. +.SH SYNOPSIS +.B py_calldist.d + +.SH DESCRIPTION +This traces Python activity from all programs running on the system with +Python provider support. + +This script prints distribution plots of elapsed time for Python +operations. Use py_calltime.d for summary reports. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_calldist.d +.PP +.SH FIELDS +.TP +1 +Filename of the Python program +.TP +2 +Type of call (func) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_calldist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_calltime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_calltime.d.1m new file mode 100644 index 000000000000..e055eb33366f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_calltime.d.1m @@ -0,0 +1,49 @@ +.TH py_calltime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_calltime.d - measure Python elapsed times for functions. +.SH SYNOPSIS +.B py_calltime.d + +.SH DESCRIPTION +This traces Python activity from all programs running on the system with +Python provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_calltime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Python program +.TP +TYPE +Type of call (func/total) +.TP +NAME +Name of call +.TP +TOTAL +Total elapsed time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_calltime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_cpudist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_cpudist.d.1m new file mode 100644 index 000000000000..825fc6401288 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_cpudist.d.1m @@ -0,0 +1,49 @@ +.TH py_cpudist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_cpudist.d - measure Python on-CPU times for functions. +.SH SYNOPSIS +.B py_cpudist.d + +.SH DESCRIPTION +This traces Python activity from all programs running on the system with +Python provider support. + +This script prints distribution plots of elapsed time for Python +operations. Use py_cputime.d for summary reports. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_cpudist.d +.PP +.SH FIELDS +.TP +1 +Filename of the Python program +.TP +2 +Type of call (func) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_cpudist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_cputime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_cputime.d.1m new file mode 100644 index 000000000000..f926204bb2bc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_cputime.d.1m @@ -0,0 +1,49 @@ +.TH py_cputime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_cputime.d - measure Python on-CPU times for functions. +.SH SYNOPSIS +.B py_cputime.d + +.SH DESCRIPTION +This traces Python activity from all programs running on the system with +Python provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_cputime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Python program +.TP +TYPE +Type of call (func/total) +.TP +NAME +Name of call (function name) +.TP +TOTAL +Total on-CPU time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_cputime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_flow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_flow.d.1m new file mode 100644 index 000000000000..3659e0f63706 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_flow.d.1m @@ -0,0 +1,60 @@ +.TH py_flow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_flow.d - snoop Python execution showing function flow. +.SH SYNOPSIS +.B py_flow.d + +.SH DESCRIPTION +This traces Python activity from all Python programs on the system +running with Python provider support. + +This watches Python function entries and returns, and indents child +function calls. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_flow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this function belongs to +.TP +FUNC +Function name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_flow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_flowinfo.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_flowinfo.d.1m new file mode 100644 index 000000000000..4a25d0db2bdb --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_flowinfo.d.1m @@ -0,0 +1,68 @@ +.TH py_flowinfo.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_flowinfo.d - snoop Python function flow with info using DTrace. +.SH SYNOPSIS +.B py_flowinfo.d + +.SH DESCRIPTION +This traces activity from all Python programs on the system that are +running with Python provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_flowinfo.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the Python program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (func) +.TP +FUNC +Python function +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_flowinfo.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_flowtime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_flowtime.d.1m new file mode 100644 index 000000000000..67882957e5ce --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_flowtime.d.1m @@ -0,0 +1,65 @@ +.TH py_flowtime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_flowtime.d - snoop Python functions with flow and delta times. +.SH SYNOPSIS +.B py_flowtime.d + +.SH DESCRIPTION +This traces shell activity from Python programs on the system that are +running with Python provider support. + +This watches Python function entries and returns, and indents child +function calls. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_flowtime.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this function belongs to +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FUNC +Python function name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_flowtime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_funccalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_funccalls.d.1m new file mode 100644 index 000000000000..8a54976199eb --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_funccalls.d.1m @@ -0,0 +1,43 @@ +.TH py_funccalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_funccalls.d - measure Python function calls using DTrace. +.SH SYNOPSIS +.B py_funccalls.d + +.SH DESCRIPTION +This traces Python activity from all running programs on the system +which support the Python DTrace provider. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_funccalls.d +.PP +.SH FIELDS +.TP +FUNC +Python function name +.TP +CALLS +Function calls during this sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_funccalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_malloc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_malloc.d.1m new file mode 100644 index 000000000000..4468da8ae2b9 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_malloc.d.1m @@ -0,0 +1,39 @@ +.TH py_malloc.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_malloc.d - Python libc malloc analysis. +.SH SYNOPSIS +.B py_malloc.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This is an expiremental script to identify who is calling malloc() for +memory allocation, and to print distribution plots of the requested bytes. +If a malloc() occured while in a Python function, then that function is +identified as responsible; else the caller of malloc() is identified as +responsible - which will be a function from the Python engine. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_malloc.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_malloc.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_mallocstk.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_mallocstk.d.1m new file mode 100644 index 000000000000..fac0a1789b54 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_mallocstk.d.1m @@ -0,0 +1,33 @@ +.TH py_mallocstk.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_mallocstk.d - Python libc malloc analysis with full stack traces. +.SH SYNOPSIS +.B py_mallocstk.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION + +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_mallocstk.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_mallocstk.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_profile.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_profile.d.1m new file mode 100644 index 000000000000..282bf48104fc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_profile.d.1m @@ -0,0 +1,54 @@ +.TH py_profile.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_profile.d - sample stack traces with Python translations using DTrace. +.SH SYNOPSIS +.B py_profile.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This samples stack traces for the process specified. This stack trace +will cross the Python engine and system libraries, and insert +translations for Python stack frames where appropriate. This is best +explained with an example stack frame output, + +libpython2.4.so.1.0`PyEval_EvalFrame+0x2fbf +[ ./func_loop.py:5 (func_c) ] +libpython2.4.so.1.0`fast_function+0xa8 +libpython2.4.so.1.0`call_function+0xda +libpython2.4.so.1.0`PyEval_EvalFrame+0xbdf +[ ./func_loop.py:11 (func_b) ] +libpython2.4.so.1.0`fast_function+0xa8 +libpython2.4.so.1.0`call_function+0xda +libpython2.4.so.1.0`PyEval_EvalFrame+0xbdf +[ ./func_loop.py:14 (func_a) ] +libpython2.4.so.1.0`fast_function+0xa8 +libpython2.4.so.1.0`call_function+0xda +libpython2.4.so.1.0`PyEval_EvalFrame+0xbdf +[ ./func_loop.py:16 (?) ] + +The lines in square brackets are the native Python frames, the rest +are the Python engine. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_profile.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_profile.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_syscalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_syscalls.d.1m new file mode 100644 index 000000000000..cd4712349714 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_syscalls.d.1m @@ -0,0 +1,49 @@ +.TH py_syscalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_syscalls.d - count Python function calls and syscalls using DTrace. +.SH SYNOPSIS +.B py_syscalls.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +Filename and function names are printed if available. +The filename for syscalls may be printed as "python", if the program +was invoked using the form "python filename" rather than running the +program with an interpreter line. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_syscalls.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Python program +.TP +TYPE +Type of call (func/syscall) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_syscalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_syscolors.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_syscolors.d.1m new file mode 100644 index 000000000000..210fa1b61f73 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_syscolors.d.1m @@ -0,0 +1,61 @@ +.TH py_syscolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_syscolors.d - trace Python function flow plus syscalls, in color. +.SH SYNOPSIS +.B py_syscolors.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This watches Python function entries and returns, and indents child +function calls. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_syscolors.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the Python program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (func/syscall) +.TP +NAME +Python function or syscall name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_syscolors.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/py_who.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/py_who.d.1m new file mode 100644 index 000000000000..e88190e6462f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/py_who.d.1m @@ -0,0 +1,49 @@ +.TH py_who.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +py_who.d - trace Python function execution by process using DTrace. +.SH SYNOPSIS +.B py_who.d + +.SH DESCRIPTION +This traces Python activity from all Python programs on the system that are +running with Python provider support. + +Filenames are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Python provider, which may change +as additional features are introduced. Check Python/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B py_who.d +.PP +.SH FIELDS +.TP +PID +Process ID of Python +.TP +UID +User ID of the owner +.TP +FUNCS +Number of function calls +.TP +FILE +Pathname of the Python program +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +py_who.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_calldist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_calldist.d.1m new file mode 100644 index 000000000000..57a975620198 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_calldist.d.1m @@ -0,0 +1,49 @@ +.TH rb_calldist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_calldist.d - measure Ruby elapsed times for types of operation. +.SH SYNOPSIS +.B rb_calldist.d + +.SH DESCRIPTION +This traces Ruby activity from all programs running on the system with +Ruby provider support. + +This script prints distribution plots of elapsed time for Ruby +operations. Use rb_calltime.d for summary reports. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_calldist.d +.PP +.SH FIELDS +.TP +1 +Filename of the Ruby program +.TP +2 +Type of call (method/obj-new/gc) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_calldist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_calls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_calls.d.1m new file mode 100644 index 000000000000..3e328f3ce7cf --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_calls.d.1m @@ -0,0 +1,49 @@ +.TH rb_calls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_calls.d - count Ruby calls using DTrace. +.SH SYNOPSIS +.B rb_calls.d + +.SH DESCRIPTION +This traces activity from all Ruby programs on the system that are +running with Ruby provider support. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_calls.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Ruby program +.TP +TYPE +Type of call (method/obj-new/...) +.TP +NAME +Descriptive name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_calls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_calltime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_calltime.d.1m new file mode 100644 index 000000000000..0787a93aa50d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_calltime.d.1m @@ -0,0 +1,49 @@ +.TH rb_calltime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_calltime.d - measure Ruby elapsed times for types of operation. +.SH SYNOPSIS +.B rb_calltime.d + +.SH DESCRIPTION +This traces Ruby activity from all programs running on the system with +Ruby provider support. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_calltime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Ruby program +.TP +TYPE +Type of call (method/obj-new/gc/total) +.TP +NAME +Name of call +.TP +TOTAL +Total elapsed time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_calltime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_cpudist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_cpudist.d.1m new file mode 100644 index 000000000000..ff4f283bbf3b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_cpudist.d.1m @@ -0,0 +1,49 @@ +.TH rb_cpudist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_cpudist.d - measure Ruby on-CPU times for types of operation. +.SH SYNOPSIS +.B rb_cpudist.d + +.SH DESCRIPTION +This traces Ruby activity from all programs running on the system with +Ruby provider support. + +This script prints distribution plots of elapsed time for Ruby +operations. Use rb_cputime.d for summary reports. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_cpudist.d +.PP +.SH FIELDS +.TP +1 +Filename of the Ruby program +.TP +2 +Type of call (method/obj-new/gc) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_cpudist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_cputime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_cputime.d.1m new file mode 100644 index 000000000000..7e8302b895a4 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_cputime.d.1m @@ -0,0 +1,49 @@ +.TH rb_cputime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_cputime.d - measure Ruby on-CPU times for types of operation. +.SH SYNOPSIS +.B rb_cputime.d + +.SH DESCRIPTION +This traces Ruby activity from all programs running on the system with +Ruby provider support. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_cputime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Ruby program +.TP +TYPE +Type of call (method/obj-new/gc/total) +.TP +NAME +Name of call +.TP +TOTAL +Total on-CPU time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_cputime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_flow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_flow.d.1m new file mode 100644 index 000000000000..fa1f51834cfd --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_flow.d.1m @@ -0,0 +1,59 @@ +.TH rb_flow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_flow.d - snoop Ruby execution showing method flow using DTrace. +.SH SYNOPSIS +.B rb_flow.d + +.SH DESCRIPTION +This traces activity from all Ruby programs on the system that are +running with Ruby provider support. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_flow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this method belongs to +.TP +CLASS::METHOD +Ruby classname and method +.SH LEGEND +.TP +\-> +method entry +.TP +<\- +method return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_flow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_flowinfo.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_flowinfo.d.1m new file mode 100644 index 000000000000..08e124fbfa25 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_flowinfo.d.1m @@ -0,0 +1,68 @@ +.TH rb_flowinfo.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_flowinfo.d - snoop Ruby function (method) flow with info using DTrace. +.SH SYNOPSIS +.B rb_flowinfo.d + +.SH DESCRIPTION +This traces activity from all Ruby programs on the system that are +running with Ruby provider support. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_flowinfo.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the Ruby program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (method) +.TP +NAME +Ruby class and method name +.SH LEGEND +.TP +\-> +method entry +.TP +<\- +method return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_flowinfo.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_flowtime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_flowtime.d.1m new file mode 100644 index 000000000000..64425b37f7be --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_flowtime.d.1m @@ -0,0 +1,62 @@ +.TH rb_flowtime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_flowtime.d - snoop Ruby function (method) flow using DTrace. +.SH SYNOPSIS +.B rb_flowtime.d + +.SH DESCRIPTION +This traces activity from all Ruby programs on the system that are +running with Ruby provider support. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_flowtime.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this method belongs to +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +CLASS::METHOD +Ruby class and method name +.SH LEGEND +.TP +\-> +method entry +.TP +<\- +method return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_flowtime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_funccalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_funccalls.d.1m new file mode 100644 index 000000000000..c4fe9fad2516 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_funccalls.d.1m @@ -0,0 +1,46 @@ +.TH rb_funccalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_funccalls.d - count Ruby function (method) calls using DTrace. +.SH SYNOPSIS +.B rb_funccalls.d + +.SH DESCRIPTION +This traces activity from all Ruby programs on the system that are +running with Ruby provider support. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_funccalls.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Ruby program +.TP +METHOD +Method name +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_funccalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_lines.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_lines.d.1m new file mode 100644 index 000000000000..4bdbabcafb57 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_lines.d.1m @@ -0,0 +1,46 @@ +.TH rb_lines.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_lines.d - trace Ruby line execution by process using DTrace. +.SH SYNOPSIS +.B rb_who.d + +.SH DESCRIPTION +This traces Ruby activity from all Ruby programs on the system that are +running with Ruby provider support. + +Filenames are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_lines.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Ruby program +.TP +LINE +Line number +.TP +COUNT +Number of times a line was executed +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_lines.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_malloc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_malloc.d.1m new file mode 100644 index 000000000000..d86bc46d14b7 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_malloc.d.1m @@ -0,0 +1,47 @@ +.TH rb_malloc.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_malloc.d - Ruby operations and libc malloc statistics. +.SH SYNOPSIS +.B rb_malloc.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_malloc.d +.PP +.SH FIELDS +.TP +1 +Filename of the Ruby program +.TP +2 +Type of operation (method/objnew/startup) +.TP +3 +Name of operation +.SH WARNING +This script is not 100% accurate; This prints libc malloc() byte +distributions by "recent" Ruby operation, which we hope will be usually +relevant. This is an experimental script that may be improved over time. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_malloc.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_objcpu.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_objcpu.d.1m new file mode 100644 index 000000000000..6d1d8b1e2928 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_objcpu.d.1m @@ -0,0 +1,36 @@ +.TH rb_objcpu.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_objcpu.d - measure Ruby object creation on-CPU time using DTrace. +.SH SYNOPSIS +.B rb_objcpu.d + +.SH DESCRIPTION +This traces Ruby activity from all programs running on the system with +Ruby provider support. + +Class names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_objcpu.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_objcpu.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_objnew.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_objnew.d.1m new file mode 100644 index 000000000000..e40f493a4998 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_objnew.d.1m @@ -0,0 +1,46 @@ +.TH rb_objnew.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_objnew.d - count Ruby object creation using DTrace. +.SH SYNOPSIS +.B rb_objnew.d + +.SH DESCRIPTION +This traces Ruby activity from all programs running on the system with +Ruby provider support. + +Filename and class names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_objnew.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Ruby program +.TP +CLASS +Class of new object +.TP +COUNT +Number of object creations during tracing +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_objnew.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_stat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_stat.d.1m new file mode 100644 index 000000000000..070faf42781d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_stat.d.1m @@ -0,0 +1,66 @@ +.TH rb_stat.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_stat.d - Ruby operation stats using DTrace. +.SH SYNOPSIS +.B rb_stat.d +[interval [count]] +.SH DESCRIPTION +This traces activity from all Ruby programs on the system that are +running with Ruby provider support. + +The numbers are counts for the interval specified. The default interval +is 1 second. + +If you see a count in "EXECS" but not in the other columns, then your +Ruby software is probably not running with the DTrace Ruby provider. +See Ruby/Readme. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_stat.d +.PP +.SH FIELDS +.TP +EXEC/s +Ruby programs executed per second, including +those without Ruby provider support +.TP +METHOD/s +Methods called, per second +.TP +OBJNEW/s +Objects created, per second +.TP +OBJFRE/s +Objects freed, per second +.TP +RAIS/s +Raises, per second +.TP +RESC/s +Rescues, per second +.TP +GC/s +Garbage collects, per second +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_stat.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_syscalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_syscalls.d.1m new file mode 100644 index 000000000000..9fbe81d3f10b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_syscalls.d.1m @@ -0,0 +1,49 @@ +.TH rb_syscalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_syscalls.d - count Ruby calls and syscalls using DTrace. +.SH SYNOPSIS +.B rb_syscalls.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +Filename and method names are printed if available. +The filename for syscalls may be printed as "ruby", if the program +was invoked using the form "ruby filename" rather than running the +program with an interpreter line. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_syscalls.d +.PP +.SH FIELDS +.TP +FILE +Filename of the Ruby program +.TP +TYPE +Type of call (method/syscall) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_syscalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_syscolors.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_syscolors.d.1m new file mode 100644 index 000000000000..bd18be9ea7d3 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_syscolors.d.1m @@ -0,0 +1,61 @@ +.TH rb_syscolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_syscolors.d - trace Ruby method flow plus syscalls, in color. +.SH SYNOPSIS +.B rb_syscolors.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This watches Ruby method entries and returns, and indents child +function calls. + +Filename and method names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_syscolors.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the Ruby program +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (method/line/syscall) +.TP +NAME +Ruby method or syscall name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_syscolors.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rb_who.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rb_who.d.1m new file mode 100644 index 000000000000..5dd13d5e7275 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rb_who.d.1m @@ -0,0 +1,49 @@ +.TH rb_who.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +rb_who.d - trace Ruby line execution by process using DTrace. +.SH SYNOPSIS +.B rb_who.d + +.SH DESCRIPTION +This traces Ruby activity from all Ruby programs on the system that are +running with Ruby provider support. + +Filenames are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Ruby provider, which may change +as additional features are introduced. Check Ruby/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B rb_who.d +.PP +.SH FIELDS +.TP +PID +Process ID of Ruby +.TP +UID +User ID of the owner +.TP +LINES +Number of times a line was executed +.TP +FILE +Pathname of the Ruby program +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +rb_who.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/readbytes.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/readbytes.d.1m new file mode 100644 index 000000000000..697339d493e1 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/readbytes.d.1m @@ -0,0 +1,47 @@ +.TH readbytes.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +readbytes.d \- read bytes by process name. Uses DTrace. +.SH SYNOPSIS +.B readbytes.d +.SH DESCRIPTION +readbytes.d is a DTrace OneLiner to a report of the number of +bytes read by process name. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B readbytes.d +.PP +.SH FIELDS +.TP +first field +This is the process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +second field +This is the number of bytes read. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +readbytes.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/readdist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/readdist.d.1m new file mode 100644 index 000000000000..e11b21c7b0b7 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/readdist.d.1m @@ -0,0 +1,54 @@ +.TH readdist.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +readdist.d \- read distrib. by process name. Uses DTrace. +.SH SYNOPSIS +.B readdist.d +.SH DESCRIPTION +readdist.d is a DTrace OneLiner to a report the read size and +number of occurrences as a frequency distribution by process name. + +This can be useful to identify the behaviour of processes +that are doing reads. Are they using many small reads, or +fewer large reads. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B readdist.d +.PP +.SH FIELDS +.TP +process name +The process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +value +The size in bytes +.TP +count +The number of occurrences that were at least this size +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +readdist.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rfileio.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rfileio.d.1m new file mode 100644 index 000000000000..08c25e9d4de2 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rfileio.d.1m @@ -0,0 +1,41 @@ +.TH rfileio.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +rfileio.d \- read file I/O stats, with cache miss rate. Uses DTrace. +.SH SYNOPSIS +.B rfileio.d +.SH DESCRIPTION +This script provides statistics on the number of reads and the bytes +read from filesystems (logical), and the number of bytes read from +disk (physical). A summary is printed every five seconds by file. + +A total miss-rate is also provided for the file system cache. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Print a summary of activity every five seconds. +# +.B rfileio.d +.PP +.SH IDEA +Richard McDougall, Solaris Internals 2nd Ed, FS Chapter. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +rfileio.d will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +rfsio.d(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rfsio.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rfsio.d.1m new file mode 100644 index 000000000000..ecbb786a84e6 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rfsio.d.1m @@ -0,0 +1,41 @@ +.TH rfsio.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +rfsio.d \- read FS I/O stats, with cache miss rate. Uses DTrace. +.SH SYNOPSIS +.B rfsio.d +.SH DESCRIPTION +This script provides statistics on the number of reads and the bytes +read from filesystems (logical), and the number of bytes read from +disk (physical). A summary is printed every five seconds by filesystem. + +A total miss-rate is also provided for the file system cache. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Print a summary of activity every five seconds. +# +.B rfsio.d +.PP +.SH IDEA +Richard McDougall, Solaris Internals 2nd Ed, FS Chapter. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +rfsio.d will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +rfileio.d(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/runocc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/runocc.d.1m new file mode 100644 index 000000000000..0ba529ffcd8e --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/runocc.d.1m @@ -0,0 +1,46 @@ +.TH runocc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +runocc.d \- run queue occupancy by CPU. Uses DTrace. +.SH SYNOPSIS +.B runocc.d +.SH DESCRIPTION +This prints the dispatcher run queue occupancy by CPU each second. +A consistant run queue occupancy is a sign of CPU saturation. + +The value is similar to that seen in "sar -q", however this is +calculated in a more accurate manner - sampling at 1000 Hertz. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable. +.SH EXAMPLES +.TP +Print %runocc by CPU every second, +# +.B runocc.d +.PP +.SH FIELDS +.TP +CPU +cpu ID +.TP +%runocc +percent run queue occupancy, sampled at 1000 Hertz +.PP +.SH SEE ALSO +Solaris Internals 2nd Ed, vol 2, CPU chapter +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +runocc.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rwbbypid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rwbbypid.d.1m new file mode 100644 index 000000000000..36ab3f24ed0a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rwbbypid.d.1m @@ -0,0 +1,48 @@ +.TH rwbbypid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +rwbbypid.d \- read/write bytes by PID. Uses DTrace. +.SH SYNOPSIS +.B rwbbypid.d +.SH DESCRIPTION +This script tracks the bytes read and written at the syscall level +by processes, printing the totals in a report. This is tracking the +successful number of bytes read or written. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B rwbbypid.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +DIR +direction, Read or Write +.TP +BYTES +total bytes +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +rwbbypid.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +rwbypid.d(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rwbypid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rwbypid.d.1m new file mode 100644 index 000000000000..869eb80e8557 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rwbypid.d.1m @@ -0,0 +1,48 @@ +.TH rwbypid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +rwbypid.d \- read/write calls by PID. Uses DTrace. +.SH SYNOPSIS +.B rwbypid.d +.SH DESCRIPTION +This script tracks the number of reads and writes at the syscall level +by processes, printing the totals in a report. This matches reads +and writes whether they succeed or not. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B rwbypid.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +DIR +direction, Read or Write +.TP +COUNT +total calls +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +rwbypid.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +rwbbypid.d(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rwbytype.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rwbytype.d.1m new file mode 100644 index 000000000000..85c8194baa9b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rwbytype.d.1m @@ -0,0 +1,54 @@ +.TH rwbytype.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +rwbytype.d \- read/write bytes by vnode type. Uses DTrace. +.SH SYNOPSIS +.B rwbytype.d +.SH DESCRIPTION +This program identifies the vnode type of read/write activity - whether +that is for regular files, sockets, character special devices, etc. This +is measuring at the application level, so file activity may well be +cached by the system. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B rwbytype.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +VNODE +vnode type (describes I/O type) +.TP +DIR +direction, Read or Write +.TP +BYTES +total bytes +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +rwbytype.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +rwbypid.d(1M), rwbbypid.d(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rwsnoop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rwsnoop.1m new file mode 100644 index 000000000000..d6e544169ce5 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rwsnoop.1m @@ -0,0 +1,104 @@ +.TH rwsnoop 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +rwsnoop \- snoop read/write events. Uses DTrace. +.SH SYNOPSIS +.B rwsnoop +[\-jPtvZ] [\-n name] [\-p PID] +.SH DESCRIPTION +This is measuring reads and writes at the application level. This +matches the syscalls read, write, pread and pwrite. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH OPTIONS +.TP +\-j +print project ID +.TP +\-P +print parent process ID +.TP +\-t +print timestamp, us +.TP +\-v +print time, string +.TP +\-Z +print zone ID +.TP +\-n name +process name to track +.TP +\-p PID +PID to track +.PP +.SH EXAMPLES +.TP +Default output, +# +.B rwsnoop +.TP +Print zone ID, +# +.B rwsnoop +-\Z +.TP +Monitor processes named "bash", +# +.B rwsnoop +\-n bash +.PP +.SH FIELDS +.TP +TIME +timestamp, us +.TP +TIMESTR +time, string +.TP +ZONE +zone ID +.TP +PROJ +project ID +.TP +UID +user ID +.TP +PID +process ID +.TP +PPID +parent process ID +.TP +CMD +command name for the process +.TP +D +direction, Read or Write +.TP +BYTES +total bytes during sample +.TP +FILE +filename, if file based. +Reads and writes that are not file based, for example with sockets, will +print "<unknown>" as the filename. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +rwsnoop will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +rwtop(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/rwtop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/rwtop.1m new file mode 100644 index 000000000000..82af043462b0 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/rwtop.1m @@ -0,0 +1,115 @@ +.TH rwtop 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +rwtop \- display top read/write bytes process. Uses DTrace. +.SH SYNOPSIS +.B rwtop +[\-Cc] [\-j|\-Z] [\-n name] [\-p PID] +[\-t top] [interval [count]] +.SH DESCRIPTION +This is measuring reads and writes at the application level. +This matches read and write system calls. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo provider. +.SH OPTIONS +.TP +\-C +don't clear the screen +.TP +\-c +print counts +.TP +\-j +print project ID +.TP +\-Z +print zone ID +.TP +\-n name +process name to track +.TP +\-p PID +PID to track +.TP +\-t top +print top number only +.PP +.SH EXAMPLES +.TP +Default output, print summary every 5 seconds +# +.B rwtop +.PP +.TP +One second samples, +# +.B rwtop +1 +.TP +Print top 10 lines only, +# +.B rwtop +\-t 10 +.TP +Monitor processes named "bash", +# +.B rwtop +\-n bash +.TP +Print 12 x 5 second samples, scrolling, +# +.B rwtop +\-C 5 12 +.PP +.SH FIELDS +.TP +PROJ +project ID +.TP +ZONE +zone ID +.TP +UID +user ID +.TP +PID +process ID +.TP +PPID +parent process ID +.TP +CMD +command name for the process +.TP +D +direction, Read or Write +.TP +BYTES +total bytes during sample +.TP +load +1 minute load average +.TP +app_r +total read Kb for sample +.TP +app_w +total write Kb for sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +rwtop will run forever until Ctrl\-C is hit, or the specified +interval is reached. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iotop(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sampleproc.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sampleproc.1m new file mode 100644 index 000000000000..0ae3a2de9009 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sampleproc.1m @@ -0,0 +1,55 @@ +.TH sampleproc 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +sampleproc \- sample processes on the CPUs. Uses DTrace. +.SH SYNOPSIS +.B sampleproc [hertz] +.SH DESCRIPTION +This program samples which process is on each CPU, at a particular +configurable rate. This can be used as an estimate for which process +is consuming the most CPU time. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - uses the ncpus_online kernel symbol. +.SH EXAMPLES +.TP +Sample at 100 hertz, +# +.B sampleproc +.TP +Sample at 400 hertz, +# +.B sampleproc +400 +.PP +.SH FIELDS +.TP +PID +process ID +.TP +COMMAND +command name +.TP +COUNT +number of samples +.TP +PERCENT +percent of CPU usage +.PP +.SH BASED ON +/usr/demo/dtrace/prof.d +.PP +.SH DOCUMENTATION +DTrace Guide "profile Provider" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +sampleproc will sample until Ctrl\-C is hit. +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sar-c.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sar-c.d.1m new file mode 100644 index 000000000000..10192fb48753 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sar-c.d.1m @@ -0,0 +1,62 @@ +.TH sar\-c.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +sar\-c.d \- sar \-c demo in DTrace. Uses DTrace. +.SH SYNOPSIS +.B sar\-c.d +.SH DESCRIPTION +This has been written to demonstrate fetching the same data as sar \-c +from DTrace. This program is intended as a starting point for other +DTrace scripts, by beginning with familiar statistics. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall and sysinfo providers. +.SH EXAMPLES +.TP +Print system call counts every second, +# +.B sar\-c.d +.PP +.SH FIELDS +.TP +scall/s +System calls +.TP +sread/s +reads +.TP +swrit/s +writes +.TP +fork/s +forks +.TP +exec/s +execs +.TP +rchar/s +read characters +.TP +wchar/s +write characters +.PP +.SH IDEA +David Rubio, who also wrote the original. +.PP +.SH NOTES +As this program does not use Kstat, there is no summary since boot line. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +sar\-c.d will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +sar(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/seeksize.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/seeksize.d.1m new file mode 100644 index 000000000000..f15743d1e197 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/seeksize.d.1m @@ -0,0 +1,51 @@ +.TH seeksize.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +seeksize.d \- print disk event seek report. Uses DTrace. +.SH SYNOPSIS +.B seeksize.d +.SH DESCRIPTION +seeksize.d is a simple DTrace program to print a report of disk +event seeks by process. + +This can be used to identify whether processes are accessing the +disks in a "random" or "sequential" manner. Sequential is often +desirable, indicated by mostly zero length seeks. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the io provider. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B seeksize.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +command and argument list +.TP +value +distance in disk blocks (sectors) +.TP +count +number of I/O operations +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +seeksize.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +iosnoop(1M), bitesize.d(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/setuids.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/setuids.d.1m new file mode 100644 index 000000000000..50d131cf551d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/setuids.d.1m @@ -0,0 +1,53 @@ +.TH setuids.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +setuids.d \- snoop setuid calls as they occur. Uses DTrace. +.SH SYNOPSIS +.B setuids.d +.SH DESCRIPTION +setuids.d is a simple DTrace program to print details of setuid +calls, where a process assumes a different UID. These are usually +related to login events. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +Default output, print setuids as they occur, +# +.B setuids.d +.PP +.SH FIELDS +.TP +UID +user ID (from) +.TP +SUID +set user ID (to) +.TP +PPID +parent process ID +.TP +PID +process ID +.TP +PCMD +parent command +.TP +CMD +command (with arguments) +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +setuids.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), bsmconv(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_calldist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_calldist.d.1m new file mode 100644 index 000000000000..760e699c0e49 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_calldist.d.1m @@ -0,0 +1,49 @@ +.TH sh_calldist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_calldist.d - measure Bourne shell elapsed times for types of operation. +.SH SYNOPSIS +.B sh_calldist.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +This script prints distribution plots of elapsed time for shell +operations. Use sh_calltime.d for summary reports. + +Filename and call names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_calldist.d +.PP +.SH FIELDS +.TP +1 +Filename of the shell or shellscript +.TP +2 +Type of call (func/builtin/cmd) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_calldist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_calls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_calls.d.1m new file mode 100644 index 000000000000..0afeaab6883f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_calls.d.1m @@ -0,0 +1,49 @@ +.TH sh_calls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_calls.d - count Bourne calls (func/builtin/cmd/subsh) using DTrace. +.SH SYNOPSIS +.B sh_calls.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_calls.d +.PP +.SH FIELDS +.TP +FILE +Filename of the shell or shellscript +.TP +TYPE +Type of call (func/builtin/cmd/subsh) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_calls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_calltime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_calltime.d.1m new file mode 100644 index 000000000000..6863d870a332 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_calltime.d.1m @@ -0,0 +1,49 @@ +.TH sh_calltime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_calltime.d - measure Bourne shell elapsed times for types of operation. +.SH SYNOPSIS +.B sh_calltime.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +Filename and call names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_calltime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the shell or shellscript +.TP +TYPE +Type of call (func/builtin/cmd/total) +.TP +NAME +Name of call +.TP +TOTAL +Total elapsed time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_calltime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_cpudist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_cpudist.d.1m new file mode 100644 index 000000000000..998e6ee8a422 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_cpudist.d.1m @@ -0,0 +1,49 @@ +.TH sh_cpudist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_cpudist.d - measure Bourne shell on-CPU times for types of operation. +.SH SYNOPSIS +.B sh_cpudist.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +This script prints distribution plots of on-CPU time for shell +operations. Use sh_cputime.d for summary reports. + +Filename and call names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_cpudist.d +.PP +.SH FIELDS +.TP +1 +Filename of the shell or shellscript +.TP +2 +Type of call (func/builtin/cmd) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_cpudist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_cputime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_cputime.d.1m new file mode 100644 index 000000000000..3c98f94e213a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_cputime.d.1m @@ -0,0 +1,49 @@ +.TH sh_cputime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_cputime.d - measure Bourne shell on-CPU times for types of operation. +.SH SYNOPSIS +.B sh_cputime.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +Filename and call names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_cputime.d +.PP +.SH FIELDS +.TP +FILE +Filename of the shell or shellscript +.TP +TYPE +Type of call (func/builtin/cmd/total) +.TP +NAME +Name of call +.TP +TOTAL +Total on-CPU time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_cputime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_flow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_flow.d.1m new file mode 100644 index 000000000000..42dc5cc4206b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_flow.d.1m @@ -0,0 +1,66 @@ +.TH sh_flow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_flow.d - snoop Bourne shell execution showing function flow using DTrace. +.SH SYNOPSIS +.B sh_flow.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +This watches shell function entries and returns, and indents child +function calls. Shell builtins are also printed. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_flow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this function belongs to +.TP +NAME +Shell function, builtin or command name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.TP +> +builtin +.TP +| +external command +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_flow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_flowinfo.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_flowinfo.d.1m new file mode 100644 index 000000000000..6fa150078214 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_flowinfo.d.1m @@ -0,0 +1,62 @@ +.TH sh_flowinfo.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_flowinfo.d - snoop Bourne shell flow with additional info. +.SH SYNOPSIS +.B sh_flowinfo.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +This watches shell function entries and returns, and indents child +function calls. Shell builtins and external commands are also printed. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_flowinfo.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the shell script +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (func/builtin/cmd/subsh) +.TP +NAME +Shell function, builtin or command name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_flowinfo.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_flowtime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_flowtime.d.1m new file mode 100644 index 000000000000..87906b6afebc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_flowtime.d.1m @@ -0,0 +1,76 @@ +.TH sh_flowtime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_flowtime.d - snoop Bourne shell execution with flow and delta times. +.SH SYNOPSIS +.B sh_flowtime.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +This watches shell function entries and returns, and indents child +function calls. Shell builtins are also printed. + +DELTAs: +-> previous line to the start of this function +<- previous line to the end of this function +> previous line to the end of this builtin +| previous line to the end of this command + +See sh_flowinfo.d for more verbose and more straightforward delta times. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_flowtime.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +FILE +Filename that this function belongs to +.TP +NAME +Shell function or builtin name +.SH LEGEND +.TP +\-> +function entry +.TP +<\- +function return +.TP +> +builtin +.TP +| +external command +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_flowtime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_lines.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_lines.d.1m new file mode 100644 index 000000000000..e3d85081ddf2 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_lines.d.1m @@ -0,0 +1,46 @@ +.TH sh_lines.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_lines.d - trace Bourne shell line execution using DTrace. +.SH SYNOPSIS +.B sh_lines.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +Filenames are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_lines.d +.PP +.SH FIELDS +.TP +FILE +Filename of the shell or shellscript +.TP +LINE +Line number +.TP +COUNT +Number of times a line was executed +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_lines.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_pidcolors.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_pidcolors.d.1m new file mode 100644 index 000000000000..3f6380ac041f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_pidcolors.d.1m @@ -0,0 +1,70 @@ +.TH sh_pidcolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_pidcolors.d - Demonstration of deeper DTrace Bourne shell analysis. +.SH SYNOPSIS +.B sh_pidcolors.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This extends sh_syscolors.d by including some "pid" provider tracing +as a starting point for deeper analysis. Currently it adds the probes, + +pid$target:a.out:e*:entry, +pid$target:a.out:e*:return + +which means, all functions from the /usr/bin/sh binary that begin with +the letter "e". This adds about 34 probes. Customise it to whichever +parts of /usr/bin/sh or the system libraries you are interested in. + +The filename for syscalls may be printed as the shell name, if the +script was invoked using the form "shell filename" rather than running +the script with an interpreter line. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_pidcolors.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the shell script +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (func/builtin/cmd/line/shell) +.TP +NAME +Shell function, builtin or command name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_pidcolors.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_stat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_stat.d.1m new file mode 100644 index 000000000000..40624f949555 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_stat.d.1m @@ -0,0 +1,59 @@ +.TH sh_stat.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_stat.d - Bourne shell operation stats using DTrace. +.SH SYNOPSIS +.B sh_stat.d +[interval [count]] +.SH DESCRIPTION +This traces activity from all sh processes on the system that are running +with sh provider support. + +The numbers are counts for the interval specified. The default interval +is 1 second. + +If you see a count in "EXECS" but not in the other columns, then sh +scripts may be running without the DTrace sh provider. See Shell/Readme. + +Filename and function names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_stat.d +.PP +.SH FIELDS +.TP +EXEC/s +Bourne shells executed per second, including +those without sh provider support +.TP +FUNC/s +Functions called, per second +.TP +BLTIN/s +Builtins called, per second +.TP +SUB-SH/s +Sub-shells called, per second +.TP +CMD/s +External commands called, per second +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_stat.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_syscalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_syscalls.d.1m new file mode 100644 index 000000000000..67d74a3ff424 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_syscalls.d.1m @@ -0,0 +1,49 @@ +.TH sh_syscalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_syscalls.d - count Bourne calls and syscalls using DTrace. +.SH SYNOPSIS +.B sh_syscalls.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +Filename and function names are printed if available. +The filename for syscalls may be printed as the shell name, if the +script was invoked using the form "shell filename" rather than running +the script with an interpreter line. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_syscalls.d +.PP +.SH FIELDS +.TP +FILE +Filename of the shell or shellscript +.TP +TYPE +Type of call (func/builtin/cmd/syscall) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_syscalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_syscolors.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_syscolors.d.1m new file mode 100644 index 000000000000..bfd1de5e8630 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_syscolors.d.1m @@ -0,0 +1,63 @@ +.TH sh_syscolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_syscolors.d - trace Bourne shell flow plus syscalls, in color. +.SH SYNOPSIS +.B sh_syscolors.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This watches shell function entries and returns, and indents child +function calls. Shell builtins, commands and lines are also printed. + +The filename for syscalls may be printed as the shell name, if the +script was invoked using the form "shell filename" rather than running +the script with an interpreter line. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_syscolors.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +FILE +Filename of the shell script +.TP +LINE +Line number of filename +.TP +TYPE +Type of call (func/builtin/cmd/line/shell) +.TP +NAME +Shell function, builtin or command name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_syscolors.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_wasted.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_wasted.d.1m new file mode 100644 index 000000000000..1b983891b049 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_wasted.d.1m @@ -0,0 +1,49 @@ +.TH sh_wasted.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_wasted.d - measure Bourne shell elapsed times for "wasted" commands. +.SH SYNOPSIS +.B sh_wasted.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This script measures "wasted" commands - those which are called externally +but are in fact builtins to the shell. Ever seen a script which calls +/usr/bin/echo needlessly? This script measures that cost. + +Filename and call names are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_wasted.d +.PP +.SH FIELDS +.TP +FILE +Filename of the shell or shellscript +.TP +NAME +Name of call +.TP +TIME +Total elapsed time for calls (us) +.SH IDEA +Mike Shapiro +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_wasted.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sh_who.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sh_who.d.1m new file mode 100644 index 000000000000..f98bef83b221 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sh_who.d.1m @@ -0,0 +1,49 @@ +.TH sh_who.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +sh_who.d - trace Bourne shell line execution by process using DTrace. +.SH SYNOPSIS +.B sh_who.d + +.SH DESCRIPTION +This traces shell activity from all Bourne shells on the system that are +running with sh provider support. + +Filenames are printed if available. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Shell provider, which may change +as additional features are introduced. Check Shell/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B sh_who.d +.PP +.SH FIELDS +.TP +PID +Process ID of the shell +.TP +UID +User ID of the owner +.TP +LINES +Number of times a line was executed +.TP +FILE +Pathname of the shell or shellscript +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +sh_who.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/shellsnoop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/shellsnoop.1m new file mode 100644 index 000000000000..a533ab0e1c1f --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/shellsnoop.1m @@ -0,0 +1,99 @@ +.TH shellsnoop 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +shellsnoop \- snoop live shell activity. Uses DTrace. +.SH SYNOPSIS +.B shellsnoop +[\-hqsv] [\-p PID] [\-u UID] +.SH DESCRIPTION +A program to print read/write details from shells, +such as keystrokes and command outputs. + +This program sounds somewhat dangerous (snooping keystrokes), but is +no more so than /usr/bin/truss, and both need root or dtrace privileges to +run. In fact, less dangerous, as we only print visible text (not password +text, for example). Having said that, it goes without saying that this +program shouldn't be used for breeching privacy of other users. + +This was written as a tool to demonstrate the capabilities of DTrace. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - this script uses the syscall provider. +.SH OPTIONS +.TP +\-q +quiet, only print data +.TP +\-s +include start time, us +.TP +\-v +include start time, string +.TP +\-p PID +PID to snoop +.TP +\-u UID +user ID to snoop +.PP +.SH EXAMPLES +.TP +Default output, +# +.B shellsnoop +.TP +human readable timestamps, +# +.B shellsnoop +\-v +.TP +watch this PID only, +# +.B shellsnoop +\-p 1892 +.TP +watch this PID data only, +# +.B shellsnoop +\-qp 1892 +.PP +.SH FIELDS +.TP +UID +user ID +.TP +PID +process ID +.TP +PPID +parent process ID +.TP +COMM +command name +.TP +DIR +direction (R read, W write) +.TP +TEXT +text contained in the read/write +.TP +TIME +timestamp for the command, us +.TP +STRTIME +timestamp for the command, string +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +shellsnoop will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/shortlived.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/shortlived.d.1m new file mode 100644 index 000000000000..cb4950726f86 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/shortlived.d.1m @@ -0,0 +1,37 @@ +.TH shortlived.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +shortlived.d \- check short lived process time. Uses DTrace. +.SH SYNOPSIS +.B shortlived.d +.SH DESCRIPTION +shortlived.d is a DTrace program to measure the time consumed by +short lived processes. + +Many short lived processes can be a burden on the system, and may be +the cause of performance problems. This program can help identify +that case. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall and proc providers. +.SH EXAMPLES +.TP +This prints a report after Ctrl\-C has been hit, +# +.B shortlived.d +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +shortlived.d will run until Ctrl\-C is hit to end the sample. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sigdist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sigdist.d.1m new file mode 100644 index 000000000000..f9f02fee9a43 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sigdist.d.1m @@ -0,0 +1,50 @@ +.TH sigdist.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +sigdist.d \- signal distribution by process. Uses DTrace. +.SH SYNOPSIS +.B sigdist.d +.SH DESCRIPTION +This is a simple DTrace script that prints the number of signals +recieved by process and signal number. This script is also available +as /usr/demo/dtrace/sig.d, where it originates. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the proc provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B sigdist.d +.PP +.SH FIELDS +.TP +SENDER +process name of sender +.TP +RECIPIENT +process name of target +.TP +SIG +signal number, see signal(3head) +.TP +COUNT +number of signals sent +.PP +.SH BASED ON +/usr/demo/dtrace/sig.d +.PP +.SH DOCUMENTATION +DTrace Guide "proc Provider" chapter (docs.sun.com) + +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +sigdist.d will sample until Ctrl\-C is hit. +.SH SEE ALSO +kill.d(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/stacksize.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/stacksize.d.1m new file mode 100644 index 000000000000..5b5a916ed397 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/stacksize.d.1m @@ -0,0 +1,42 @@ +.TH stacksize.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +stacksize.d \- measure stack size for running threads. Uses DTrace. +.SH SYNOPSIS +.B stacksize.d +.SH DESCRIPTION +This samples the user stack size by process name, and prints a +distribution plot so that the average stack size can be easily +identified. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sched provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B stacksize.d +.PP +.SH FIELDS +.TP +value +size of the user stack +.TP +count +number of samples at this size +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +stacksize.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Jonathan Adams +.SH SEE ALSO +pmap(1), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/statsnoop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/statsnoop.1m new file mode 100644 index 000000000000..9a1011dac67a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/statsnoop.1m @@ -0,0 +1,140 @@ +.TH statsnoop 1m "$Date:: 2007-09-23 #$" "USER COMMANDS" +.SH NAME +statsnoop \- snoop file stats as they occur. Uses DTrace. +.SH SYNOPSIS +.B statsnoop +[\-a|\-A|\-ceghsvxZ] [\-f pathname] [\-n name] [\-p PID] +.SH DESCRIPTION +statsnoop traces the stat variety of syscalls. +As a process issues a file stat, details +such as UID, PID and pathname are printed out. + +The returned file descriptor is printed, +a value of -1 indicates an error. This can be useful +for troubleshooting to determine if appliacions are attempting to +stat files that do not exist. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH OPTIONS +.TP +\-a +print all data +.TP +\-A +dump all data, space delimited +.TP +\-c +print current working directory of process +.TP +\-e +print errno value +.TP +\-g +print full command arguments +.TP +\-s +print start time, us +.TP +\-v +print start time, string +.TP +\-x +only print failed stats +.TP +\-Z +print zonename +.TP +\-f pathname +file pathname to snoop +.TP +\-n name +process name to snoop +.TP +\-p PID +process ID to snoop +.PP +.SH EXAMPLES +.TP +Default output, print file stats by process as they occur, +# +.B statsnoop +.PP +.TP +Print human readable timestamps, +# +.B statsnoop +\-v +.PP +.TP +See error codes, +# +.B statsnoop +\-e +.PP +.TP +Snoop this file only, +# +.B statsnoop +\-f /etc/passwd +.PP +.SH FIELDS +.TP +ZONE +Zone name +.TP +UID +User ID +.TP +PID +Process ID +.TP +PPID +Parent Process ID +.TP +FD +File Descriptor (-1 is error) +.TP +ERR +errno value (see /usr/include/sys/errno.h) +.TP +CWD +current working directory of process +.TP +PATH +pathname for file stat +.TP +COMM +command name for the process +.TP +ARGS +argument listing for the process +.TP +TIME +timestamp for the stat event, us +.TP +STRTIME +timestamp for the stat event, string +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +statsnoop will run forever until Ctrl\-C is hit. +.SH BUGS +occasionally the pathname for the file stat cannot be read +and the following error will be seen, + +dtrace: error on enabled probe ID 6 (...): invalid address + +this is normal behaviour. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/swapinfo.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/swapinfo.d.1m new file mode 100644 index 000000000000..322d29d1608d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/swapinfo.d.1m @@ -0,0 +1,88 @@ +.TH swapinfo.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +swapinfo.d \- print virtual memory info. Uses DTrace. +.SH SYNOPSIS +.B swapinfo.d +.SH DESCRIPTION +Prints swap usage details for RAM and disk based swap. + +This script is UNDER CONSTRUCTION, check for newer versions. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - uses various kernel symbols. +.SH FIELDS +.TP +RAM Total +Total RAM installed +.TP +RAM Unusable +RAM consumed by the OBP and TSBs +.TP +RAM Kernel +Kernel resident in RAM (and usually locked) +.TP +RAM Locked +Locked memory pages from swap (Anon) +.TP +RAM Used +anon + exec + file pages used +.TP +RAM Free +free memory + page cache free +.TP +Disk Total +Total disk swap configured +.TP +Disk Resv +Disk swap allocated + reserved +.TP +Disk Avail +Disk swap available for reservation +.TP +Swap Total +Total Virtual Memory usable +.TP +Swap Resv +VM allocated + reserved +.TP +Swap Avail +VM available for reservation +.TP +Swap MinFree +VM kept free from reservations +.PP +.SH EXAMPLES +.TP +Print info, +# +.B swapinfo.d +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH ADDITIONAL RESOURCES +swapstat - K9Toolkit + +vmstat 1 2; swap -s; echo ::memstat | mdb -k + +RMCmem - The MemTool Package + +RICHPse - The SE Toolkit + +"Clearing up swap space confusion" Unix Insider, Adrian Cockcroft + +"Solaris Internals", Jim Mauro, Richard McDougall + +/usr/include/vm/anon.h, /usr/include/sys/systm.h + +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/sysbypid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/sysbypid.d.1m new file mode 100644 index 000000000000..b956f1243db3 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/sysbypid.d.1m @@ -0,0 +1,50 @@ +.TH sysbypid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +sysbypid.d \- system stats by PID. Uses DTrace. +.SH SYNOPSIS +.B sysbypid.d +.SH DESCRIPTION +sysbypid.d is a simple DTrace program to print System +statistics by process. + +The system statistics are documented in the cpu_sysinfo struct +in the /usr/include/sys/sysinfo.h file; and also in the sysinfo provider +chapter of the DTrace Guide, http://docs.sun.com/db/doc/817-6223. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo provider. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B sysbypid.d +.PP +.SH FIELDS +.TP +EXEC +process name +.TP +PID +process ID +.TP +VM +Virtual Memory statistic +.TP +VALUE +Value by which statistic was incremented +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +sysbypid.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), vmstat(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/syscallbypid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/syscallbypid.d.1m new file mode 100644 index 000000000000..e799dba9ebfe --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/syscallbypid.d.1m @@ -0,0 +1,50 @@ +.TH syscallbypid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +syscallbypid.d \- syscalls by process ID. Uses DTrace. +.SH SYNOPSIS +.B syscallbypid.d +.SH DESCRIPTION +This reports the number of each type of system call made by PID. +This is useful to identify which process is causing the most +system calls. + +This is based on a script from DExplorer. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B syscallbypid.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +SYSCALL +system call name +.TP +COUNT +number of system calls made in this sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +syscallbypid.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +procsystime(1M), dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/syscallbyproc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/syscallbyproc.d.1m new file mode 100644 index 000000000000..bb3234824826 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/syscallbyproc.d.1m @@ -0,0 +1,50 @@ +.TH syscallbyproc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +syscallbyproc.d \- syscalls by process name. Uses DTrace. +.SH SYNOPSIS +.B syscallbyproc.d +.SH DESCRIPTION +syscallbyproc.d is a DTrace OneLiner to a report of the number of +system calls made by process name. + +This is useful to identify which process is causing the most +system calls. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Any +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B syscallbyproc.d +.PP +.SH FIELDS +.TP +first field +This is the process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +second field +This is the count, the number of system calls made. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +syscallbyproc.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +procsystime(1M), dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/syscallbysysc.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/syscallbysysc.d.1m new file mode 100644 index 000000000000..c8f34f2d047c --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/syscallbysysc.d.1m @@ -0,0 +1,47 @@ +.TH syscallbysysc.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +syscallbysysc.d \- syscalls by syscall. Uses DTrace. +.SH SYNOPSIS +.B syscallbysysc.d +.SH DESCRIPTION +syscallbysysc.d is a DTrace OneLiner to a report of the number of +each type of system call made. + +This is useful to identify which system call is the most common. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Any +.SH STABILITY +stable - needs the syscall provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B syscallbysysc.d +.PP +.SH FIELDS +.TP +first field +This is the system call type. Most have man pages in section 2. +.TP +second field +This is the count, the number of occurrances for this system call. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +syscallbysysc.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +procsystime(1M), dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calldist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calldist.d.1m new file mode 100644 index 000000000000..351a3f431eee --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calldist.d.1m @@ -0,0 +1,47 @@ +.TH tcl_calldist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_calldist.d - measure Tcl elapsed time for different types of operation. +.SH SYNOPSIS +.B tcl_calldist.d +[top] +eg, +tcl_calldist.d # default, truncate to 10 lines +tcl_calldist.d 25 # truncate each report section to 25 lines +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_calldist.d +.PP +.SH FIELDS +.TP +1 +Process ID +.TP +2 +Type of call (proc/cmd/total) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_calldist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calls.d.1m new file mode 100644 index 000000000000..df65cde58745 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calls.d.1m @@ -0,0 +1,68 @@ +.TH tcl_calls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_calls.d - count Tcl calls (proc/cmd) using DTrace. +.SH SYNOPSIS +.B tcl_calls.d + +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +TYPEs: +proc procedure +cmd command + +PORTIONS: Copyright (c) 2007 Brendan Gregg. + +CDDL HEADER START + +The contents of this file are subject to the terms of the +Common Development and Distribution License, Version 1.0 only +(the "License"). You may not use this file except in compliance +with the License. + +You can obtain a copy of the license at Docs/cddl1.txt +or http://www.opensolaris.org/os/licensing. +See the License for the specific language governing permissions +and limitations under the License. + +CDDL HEADER END + +09-Sep-2007 Brendan Gregg Created this. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_calls.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (see below) +.TP +NAME +Name of proc or cmd call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_calls.d will run until Ctrl-C is hit. +.SH AUTHOR + +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calltime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calltime.d.1m new file mode 100644 index 000000000000..14074af76cbd --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_calltime.d.1m @@ -0,0 +1,50 @@ +.TH tcl_calltime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_calltime.d - measure Tcl elapsed times for different types of operation. +.SH SYNOPSIS +.B tcl_calltime.d +[top] +eg, +tcl_calltime.d # default, truncate to 10 lines +tcl_calltime.d 25 # truncate each report section to 25 lines +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_calltime.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (proc/cmd/total) +.TP +NAME +Name of call +.TP +TOTAL +Total elapsed time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_calltime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_cpudist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_cpudist.d.1m new file mode 100644 index 000000000000..7ae55d865885 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_cpudist.d.1m @@ -0,0 +1,47 @@ +.TH tcl_cpudist.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_cpudist.d - measure Tcl on-CPU time for different types of operation. +.SH SYNOPSIS +.B tcl_cpudist.d +[top] +eg, +tcl_cpudist.d # default, truncate to 10 lines +tcl_cpudist.d 25 # truncate each report section to 25 lines +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_cpudist.d +.PP +.SH FIELDS +.TP +1 +Process ID +.TP +2 +Type of call (proc/cmd/total) +.TP +3 +Name of call +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_cpudist.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_cputime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_cputime.d.1m new file mode 100644 index 000000000000..efbac89f7822 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_cputime.d.1m @@ -0,0 +1,50 @@ +.TH tcl_cputime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_cputime.d - measure Tcl on-CPU times for different types of operation. +.SH SYNOPSIS +.B tcl_cputime.d +[top] +eg, +tcl_cputime.d # default, truncate to 10 lines +tcl_cputime.d 25 # truncate each report section to 25 lines +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_cputime.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (proc/cmd/total) +.TP +NAME +Name of call +.TP +TOTAL +Total on-CPU time for calls (us) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_cputime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_flow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_flow.d.1m new file mode 100644 index 000000000000..bba2e3a17780 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_flow.d.1m @@ -0,0 +1,66 @@ +.TH tcl_flow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_flow.d - snoop Tcl execution showing procedure flow using DTrace. +.SH SYNOPSIS +.B tcl_flow.d + +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +This watches Tcl method entries and returns, and indents child +method calls. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_flow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +PID +Process ID +.TP +CALL +Tcl command or procedure name +.SH LEGEND +.TP +\-> +procedure entry +.TP +<\- +procedure return +.TP +> +command entry +.TP +< +command return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_flow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_flowtime.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_flowtime.d.1m new file mode 100644 index 000000000000..56194d2d9ce6 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_flowtime.d.1m @@ -0,0 +1,69 @@ +.TH tcl_flowtime.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_flowtime.d - snoop Tcl execution showing procedure flow and delta times. +.SH SYNOPSIS +.B tcl_flowtime.d + +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +This watches Tcl method entries and returns, and indents child +method calls. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_flowtime.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +TIME(us) +Time since boot, us +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +CALL +Tcl command or procedure name +.SH LEGEND +.TP +\-> +procedure entry +.TP +<\- +procedure return +.TP +> +command entry +.TP +< +command return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_flowtime.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_ins.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_ins.d.1m new file mode 100644 index 000000000000..f3ab7feb99bc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_ins.d.1m @@ -0,0 +1,50 @@ +.TH tcl_calls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_calls.d - count Tcl calls (method/...) using DTrace. +.SH SYNOPSIS +.B tcl_calls.d + +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +TYPEs: +inst instruction +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_calls.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (see below) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_calls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_insflow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_insflow.d.1m new file mode 100644 index 000000000000..877757d2291c --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_insflow.d.1m @@ -0,0 +1,69 @@ +.TH tcl_insflow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_insflow.d - snoop Tcl execution showing procedure flow and delta times. +.SH SYNOPSIS +.B tcl_insflow.d + +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +This watches Tcl method entries and returns, and indents child +method calls. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_insflow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +TIME(us) +Time since boot, us +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +TYPE +Type of call (proc/cmd/inst) +.TP +CALL +Tcl command or procedure name +.SH LEGEND +.TP +proc +procedure +.TP +cmd +command +.TP +inst +instruction +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_insflow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_proccalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_proccalls.d.1m new file mode 100644 index 000000000000..9fda802351fd --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_proccalls.d.1m @@ -0,0 +1,44 @@ +.TH tcl_methodcalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_methodcalls.d - count Tcl method calls DTrace. +.SH SYNOPSIS +.B tcl_methodcalls.d + +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_methodcalls.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +COUNT +Number of calls during sample +.TP +PROCEDURE +Tcl procedure name +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_methodcalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_procflow.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_procflow.d.1m new file mode 100644 index 000000000000..aa79e913b0ca --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_procflow.d.1m @@ -0,0 +1,60 @@ +.TH tcl_procflow.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_procflow.d - snoop Tcl execution showing procedure flow using DTrace. +.SH SYNOPSIS +.B tcl_procflow.d + +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +This watches Tcl method entries and returns, and indents child +method calls. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_procflow.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +TIME(us) +Time since boot, us +.TP +PID +Process ID +.TP +PROCEDURE +Tcl procedure name +.SH LEGEND +.TP +\-> +proc entry +.TP +<\- +proc return +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_procflow.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_stat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_stat.d.1m new file mode 100644 index 000000000000..280b8c0d2acc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_stat.d.1m @@ -0,0 +1,61 @@ +.TH tcl_stat.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_stat.d - Tcl operation stats using DTrace. +.SH SYNOPSIS +.B tcl_stat.d +[interval [count]] +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +The numbers are counts for the interval specified. The default interval +is 1 second. + +If you see a count in "EXECS" but not in the other columns, then you +may have older Tcl software that does not have the integrated DTrace +provider (or newer software where the provider has changed). +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_stat.d +.PP +.SH FIELDS +.TP +EXEC/s +Tcl programs executed per second, including +those without Tcl provider support +.TP +PROC/s +Procedures called, per second +.TP +CMD/s +Commands created, per second +.TP +OBJNEW/s +Objects created, per second +.TP +OBJFRE/s +Objects freed, per second +.TP +OP/s +Bytecode operations, per second +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_stat.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_syscalls.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_syscalls.d.1m new file mode 100644 index 000000000000..ef4e5fe1f506 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_syscalls.d.1m @@ -0,0 +1,47 @@ +.TH tcl_syscalls.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_syscalls.d - count Tcl calls and syscalls using DTrace. +.SH SYNOPSIS +.B tcl_syscalls.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_syscalls.d +.PP +.SH FIELDS +.TP +PID +Process ID +.TP +TYPE +Type of call (method/syscall) +.TP +NAME +Name of call +.TP +COUNT +Number of calls during sample +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_syscalls.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_syscolors.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_syscolors.d.1m new file mode 100644 index 000000000000..4b920d55e327 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_syscolors.d.1m @@ -0,0 +1,59 @@ +.TH tcl_syscolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_syscolors.d - trace Tcl program flow plus syscalls, in color. +.SH SYNOPSIS +.B tcl_syscolors.d +{ \-p PID | \-c cmd } +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +This watches Tcl method entries and returns, and indents child +method calls. +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_syscolors.d +.PP +.SH FIELDS +.TP +C +CPU-id +.TP +PID +Process ID +.TP +TID +Thread ID +.TP +DELTA(us) +Elapsed time from previous line to this line +.TP +TYPE +Type of call (proc/cmd/syscall) +.TP +NAME +Tcl proc/cmd or syscall name +.SH WARNING +Watch the first column carefully, it prints the CPU-id. If it +changes, then it is very likely that the output has been shuffled. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_syscolors.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcl_who.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_who.d.1m new file mode 100644 index 000000000000..f6a69944ea29 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcl_who.d.1m @@ -0,0 +1,54 @@ +.TH tcl_who.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS" +.SH NAME +tcl_who.d - trace Tcl calls by process using DTrace. +.SH SYNOPSIS +.B tcl_who.d + +.SH DESCRIPTION +This traces activity from all Tcl processes on the system with DTrace +provider support (tcl8.4.16). + +Calls is a measure of activity, and is a count of the procedures and +commands that Tcl called. + +The argument list is truncated at 55 characters (up to 80 is easily +available). To easily read the full argument list, use other system tools; +on Solaris use "pargs PID". +.SH OS +Any +.SH STABILITY +Evolving - uses the DTrace Tcl provider, which may change +as additional features are introduced. Check Tcl/Readme +to see what version these scripts are based on. +.SH EXAMPLES +.TP +Default output, +# +.B tcl_who.d +.PP +.SH FIELDS +.TP +PID +Process ID of Tcl +.TP +UID +User ID of the owner +.TP +CALLS +Number of calls made (proc + cmd) +.TP +ARGS +Process name and arguments +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Examples, Notes and Docs directories. The example files may be +especially useful as they aim to demonstrate how to interpret +the output. +.SH EXIT +tcl_who.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop.1m new file mode 100644 index 000000000000..7fff62c535c6 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop.1m @@ -0,0 +1,116 @@ +.TH tcpsnoop 1m "$Date:: 2007-10-04 #$" "USER COMMANDS" +.SH NAME +tcpsnoop \- snoop TCP network packets by process. Uses DTrace. +.SH SYNOPSIS +.B tcpsnoop +[\-a|hjsvZ] [\-n name] [\-p pid] +.SH DESCRIPTION +This analyses TCP network packets and prints the responsible PID and UID, +plus standard details such as IP address and port. This captures traffic +of newly created TCP connections that were established while this program +was running. It can help identify which processes is causing TCP traffic. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris 10 3/05 +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH OPTIONS +.TP +\-a +print all data +.TP +\-j +print project ID +.TP +\-s +print time, us +.TP +\-v +print time, string +.TP +\-Z +print zone ID +.TP +\-n name +command name to snoop +.TP +\-p PID +process ID to snoop +.PP +.SH EXAMPLES +.TP +Default output, snoop TCP network packets with details, +# +.B tcpsnoop +.TP +Print human readable timestamps, +# +.B tcpsnoop +\-v +.TP +Print zonename, +# +.B tcpsnoop +\-Z +.TP +Print sshd traffic only, +# +.B tcpsnoop +\-n sshd +.PP +.SH FIELDS +.TP +UID +user ID +.TP +PID +process ID +.TP +CMD +command name +.TP +LADDR +local IP address +.TP +RADDR +remote IP address +.TP +LPORT +local port number +.TP +RPORT +remote port number +.TP +DR +direction +.TP +SIZE +packet size, bytes +.TP +TIME +timestamp, us +.TP +STRTIME +human readable timestamp, string +.TP +ZONE +zone ID +.TP +PROJ +project ID +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +tcpsnoop will print traffic until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +tcptop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop.d.1m new file mode 100644 index 000000000000..e1cfd3c13f4d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop.d.1m @@ -0,0 +1,68 @@ +.TH tcpsnoop.d 1m "$Date:: 2007-10-04 #$" "USER COMMANDS" +.SH NAME +tcpsnoop.d \- snoop TCP network packets by process. DTrace. +.SH SYNOPSIS +.B tcpsnoop.d +.SH DESCRIPTION +This analyses TCP network packets and prints the responsible PID and UID, +plus standard details such as IP address and port. This captures traffic +of newly created TCP connections that were established while this program +was running. It can help identify which processes is causing TCP traffic. + +This is a DTrace only version of "tcpsnoop" - an enhanced program that +provides command line options. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris 10 3/05 +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Default output, snoop TCP network packets with details, +# +.B tcpsnoop.d +.PP +.SH FIELDS +.TP +UID +user ID +.TP +PID +process ID +.TP +CMD +command name +.TP +LADDR +local IP address +.TP +RADDR +remote IP address +.TP +LPORT +local port number +.TP +RPORT +remote port number +.TP +DR +direction +.TP +SIZE +packet size, bytes +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +tcpsnoop.d will print traffic until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +tcpsnoop(1M), tcptop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop_snv.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop_snv.1m new file mode 100644 index 000000000000..36e880d78317 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop_snv.1m @@ -0,0 +1,116 @@ +.TH tcpsnoop 1m "$Date:: 2007-10-04 #$" "USER COMMANDS" +.SH NAME +tcpsnoop \- snoop TCP network packets by process. Uses DTrace. +.SH SYNOPSIS +.B tcpsnoop +[\-a|hjsvZ] [\-n name] [\-p pid] +.SH DESCRIPTION +This analyses TCP network packets and prints the responsible PID and UID, +plus standard details such as IP address and port. This captures traffic +of newly created TCP connections that were established while this program +was running. It can help identify which processes is causing TCP traffic. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris Nevada / OpenSolaris, circa late 2007 +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH OPTIONS +.TP +\-a +print all data +.TP +\-j +print project ID +.TP +\-s +print time, us +.TP +\-v +print time, string +.TP +\-Z +print zone ID +.TP +\-n name +command name to snoop +.TP +\-p PID +process ID to snoop +.PP +.SH EXAMPLES +.TP +Default output, snoop TCP network packets with details, +# +.B tcpsnoop +.TP +Print human readable timestamps, +# +.B tcpsnoop +\-v +.TP +Print zonename, +# +.B tcpsnoop +\-Z +.TP +Print sshd traffic only, +# +.B tcpsnoop +\-n sshd +.PP +.SH FIELDS +.TP +UID +user ID +.TP +PID +process ID +.TP +CMD +command name +.TP +LADDR +local IP address +.TP +RADDR +remote IP address +.TP +LPORT +local port number +.TP +RPORT +remote port number +.TP +DR +direction +.TP +SIZE +packet size, bytes +.TP +TIME +timestamp, us +.TP +STRTIME +human readable timestamp, string +.TP +ZONE +zone ID +.TP +PROJ +project ID +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +tcpsnoop will print traffic until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +tcptop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop_snv.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop_snv.d.1m new file mode 100644 index 000000000000..79bfda36285c --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcpsnoop_snv.d.1m @@ -0,0 +1,68 @@ +.TH tcpsnoop.d 1m "$Date:: 2007-10-04 #$" "USER COMMANDS" +.SH NAME +tcpsnoop.d \- snoop TCP network packets by process. DTrace. +.SH SYNOPSIS +.B tcpsnoop.d +.SH DESCRIPTION +This analyses TCP network packets and prints the responsible PID and UID, +plus standard details such as IP address and port. This captures traffic +of newly created TCP connections that were established while this program +was running. It can help identify which processes is causing TCP traffic. + +This is a DTrace only version of "tcpsnoop" - an enhanced program that +provides command line options. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris Nevada / OpenSolaris, circa late 2007 +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Default output, snoop TCP network packets with details, +# +.B tcpsnoop.d +.PP +.SH FIELDS +.TP +UID +user ID +.TP +PID +process ID +.TP +CMD +command name +.TP +LADDR +local IP address +.TP +RADDR +remote IP address +.TP +LPORT +local port number +.TP +RPORT +remote port number +.TP +DR +direction +.TP +SIZE +packet size, bytes +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +tcpsnoop.d will print traffic until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +tcpsnoop(1M), tcptop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcpstat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcpstat.d.1m new file mode 100644 index 000000000000..4db577c446a5 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcpstat.d.1m @@ -0,0 +1,58 @@ +.TH tcpstat.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +tcpstat.d \- print TCP statistics. Uses DTrace. +.SH SYNOPSIS +.B tcpstat.d +.SH DESCRIPTION +tcpstat.d is a DTrace program to print TCP statistics every second, +retrieved from the MIB provider. + +This program can be used to help identify how utilised the network +interfaces may be, as well as TCP transmission errors. + +The TCP statistics are documented in the mib2_tcp struct +in /usr/include/inet/mib2.h; and also in the mib provider +chapter of the DTrace Guide, found at +http://docs.sun.com/db/doc/817-6223. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the mib provider. +.SH EXAMPLES +.TP +Print statistics every second, +# +.B tcpstat.d +.PP +.SH FIELDS +.TP +TCP_out +TCP bytes sent +.TP +TCP_outRe +TCP bytes retransmitted +.TP +TCP_in +TCP bytes received +.TP +TCP_inDup +TCP bytes received duplicated +.TP +TCP_inUn +TCP bytes received out of order +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +tcpstat.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +nicstat(1M), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcptop.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcptop.1m new file mode 100644 index 000000000000..156aaf50fc69 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcptop.1m @@ -0,0 +1,111 @@ +.TH tcptop 1m "$Date:: 2007-10-04 #$" "USER COMMANDS" +.SH NAME +tcptop \- display top TCP network packets by process. Uses DTrace. +.SH SYNOPSIS +.B tcptop +[-Ch] [-j|-Z] [interval [count]] +.SH DESCRIPTION +This analyses TCP network packets and prints the responsible PID and UID, +plus standard details such as IP address and port. This captures traffic +of newly created TCP connections that were established while this program +was running. It can help identify which processes is causing TCP traffic. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris 10 3/05 +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH OPTIONS +.TP +\-C +don't clear the screen +.TP +\-j +print project IDs +.TP +\-Z +print zone IDs +.TP +interval +sample seconds between refreshing the screen +.TP +count +number of samples +.PP +.SH EXAMPLES +.TP +Print a report every 5 seconds, +# +.B tcptop +.TP +Don't clear the screen, scrolling output, +# +.B tcptop +\-C +.TP +Print project IDs, +# +.B tcptop +\-j +.TP +Print zone IDs, +# +.B tcptop +\-Z +.PP +.SH FIELDS +.TP +UID +user ID +.TP +PID +process ID +.TP +CMD +command name +.TP +LADDR +local IP address +.TP +RADDR +remote IP address +.TP +LPORT +local port number +.TP +RPORT +remote port number +.TP +SIZE +packet size, bytes +.TP +load +1 minute load average +.TP +TCPin +total TCP inbound payload data +.TP +TCPout +total TCP outbound payload data +.TP +ZONE +zone ID +.TP +PROJ +project ID +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +tcptop will print reports until Ctrl\-C is hit, or the specified +count is reached. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +tcpsnoop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcptop_snv.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcptop_snv.1m new file mode 100644 index 000000000000..9ac14ac3a427 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcptop_snv.1m @@ -0,0 +1,111 @@ +.TH tcptop 1m "$Date:: 2007-10-04 #$" "USER COMMANDS" +.SH NAME +tcptop \- display top TCP network packets by process. Uses DTrace. +.SH SYNOPSIS +.B tcptop +[-Ch] [-j|-Z] [interval [count]] +.SH DESCRIPTION +This analyses TCP network packets and prints the responsible PID and UID, +plus standard details such as IP address and port. This captures traffic +of newly created TCP connections that were established while this program +was running. It can help identify which processes is causing TCP traffic. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris Nevada / OpenSolaris, circa late 2007 +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH OPTIONS +.TP +\-C +don't clear the screen +.TP +\-j +print project IDs +.TP +\-Z +print zone IDs +.TP +interval +sample seconds between refreshing the screen +.TP +count +number of samples +.PP +.SH EXAMPLES +.TP +Print a report every 5 seconds, +# +.B tcptop +.TP +Don't clear the screen, scrolling output, +# +.B tcptop +\-C +.TP +Print project IDs, +# +.B tcptop +\-j +.TP +Print zone IDs, +# +.B tcptop +\-Z +.PP +.SH FIELDS +.TP +UID +user ID +.TP +PID +process ID +.TP +CMD +command name +.TP +LADDR +local IP address +.TP +RADDR +remote IP address +.TP +LPORT +local port number +.TP +RPORT +remote port number +.TP +SIZE +packet size, bytes +.TP +load +1 minute load average +.TP +TCPin +total TCP inbound payload data +.TP +TCPout +total TCP outbound payload data +.TP +ZONE +zone ID +.TP +PROJ +project ID +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +tcptop will print reports until Ctrl\-C is hit, or the specified +count is reached. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +tcpsnoop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/tcpwdist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/tcpwdist.d.1m new file mode 100644 index 000000000000..626d66e74f25 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/tcpwdist.d.1m @@ -0,0 +1,60 @@ +.TH tcpwdist.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +tcpwdist.d \- simple TCP write dist by process. Uses DTrace. +.SH SYNOPSIS +.B tcpwdist.d +.SH DESCRIPTION +This measures the size of writes from applications to the TCP level, which +may well be much larger than the MTU size (this is application writes not +packet writes). It can help identify which process is creating network +traffic, and the size of the writes by that application. It uses a simple +probe that produces meaningful output for most protocols. + +Tracking TCP activity by process is complex for a number of reasons, +the greatest is that inbound TCP traffic is asynchronous to the process. +The easiest TCP traffic to match is writes, which this script demonstrates. +However there are still issues - for an inbound telnet connection the +writes are associated with the command, for example "ls -l", not something +meaningful such as "in.telnetd". + +Scripts that match TCP traffic properly include tcpsnoop and tcptop. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B tcpwdist.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +command and argument list +.TP +value +TCP write payload size in bytes +.TP +count +number of writes +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +tcpwdist.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +tcpsnoop(1M), tcptop(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/threaded.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/threaded.d.1m new file mode 100644 index 000000000000..c17ad9acc9de --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/threaded.d.1m @@ -0,0 +1,50 @@ +.TH threaded.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +threaded.d \- sample multi-threaded CPU usage. Uses DTrace. +.SH SYNOPSIS +.B threaded.d +.SH DESCRIPTION +This measures thread IDs as a process runs across multiple CPUs. +It is a simple script that can help determine if a multi-threaded +application is effectively using it's threads, or if the threads have +serialised. See the example file in Docs/Examples/threaded_example.txt +for a demonstration. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Any +.SH STABILITY +stable. +.SH EXAMPLES +.TP +This runs until Ctrl\-C is hit. +# +.B threaded.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +value +thread ID +.TP +count +number of samples +.PP +.SH SEE ALSO +prstat \-L +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +threaded.d will run until Ctrl\-C is hit. +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/topsyscall.1m b/cddl/contrib/dtracetoolkit/Man/man1m/topsyscall.1m new file mode 100644 index 000000000000..34734546ac34 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/topsyscall.1m @@ -0,0 +1,73 @@ +.TH topsyscall 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +topsyscall \- top syscalls by syscall name. Uses DTrace. +.SH SYNOPSIS +.B topsyscall +[-Cs] [interval [count]] +.SH DESCRIPTION +This program continually prints a report of the top system calls, +and refreshes the display every 1 second or as specified at the +command line. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - uses the hp_avenrun kernel symbol. +.SH OPTIONS +.TP +\-C +don't clear the screen +.TP +\-s +print per second values +.PP +.SH EXAMPLES +.TP +Default output, 1 second updates, +# +.B topsyscall +.TP +Print every 5 seconds, +# +.B topsyscall +5 +.TP +Print a scrolling output, +# +.B topsyscall +\-C +.PP +.SH FIELDS +.TP +load avg +load averages, see uptime(1) +.TP +syscalls +total syscalls in this interval +.TP +syscalls/s +syscalls per second +.TP +SYSCALL +system call name +.TP +COUNT +total syscalls in this interval +.TP +COUNT/s +syscalls per second +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +topsyscall will run until Ctrl\-C is hit, or the specified +interval is reached. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), prstat(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/topsysproc.1m b/cddl/contrib/dtracetoolkit/Man/man1m/topsysproc.1m new file mode 100644 index 000000000000..2f5e1c39d2ce --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/topsysproc.1m @@ -0,0 +1,75 @@ +.TH topsysproc 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +topsysproc \- top syscalls by process name. Uses DTrace. +.SH SYNOPSIS +.B topsysproc +[-Cs] [interval [count]] +.SH DESCRIPTION +This program continually prints a report of the number of system calls +by process name, and refreshes the display every 1 second or as specified +at the command line. Similar data can be fetched with "prstat -m". + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - uses the hp_avenrun kernel symbol. +.SH OPTIONS +.TP +\-C +don't clear the screen +.TP +\-s +print per second values +.PP +.SH EXAMPLES +.TP +Default output, 1 second updates, +# +.B topsysproc +.TP +Print every 5 seconds, +# +.B topsysproc +5 +.TP +Print a scrolling output, +# +.B topsysproc +\-C +.PP +.SH FIELDS +.TP +load avg +load averages, see uptime(1) +.TP +syscalls +total syscalls in this interval +.TP +syscalls/s +syscalls per second +.TP +PROCESS +process name +.TP +COUNT +total syscalls in this interval +.TP +COUNT/s +syscalls per second +.PP +.SH NOTES +There may be several PIDs with the same process name. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +topsysproc will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), prstat(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/udpstat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/udpstat.d.1m new file mode 100644 index 000000000000..340f659d06bc --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/udpstat.d.1m @@ -0,0 +1,55 @@ +.TH udpstat.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +udpstat.d \- print UDP statistics. Uses DTrace. +.SH SYNOPSIS +.B udpstat.d +.SH DESCRIPTION +udpstat.d is a DTrace program to print UDP statistics every second, +retrieved from the MIB provider. + +The UDP statistics are documented in the mib2_tcp struct +in /usr/include/inet/mib2.h; and also in the mib provider +chapter of the DTrace Guide, found at +http://docs.sun.com/db/doc/817-6223. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the mib provider. +.SH EXAMPLES +.TP +Print statistics every second, +# +.B udpstat.d +.PP +.SH FIELDS +.TP +UDP_out +UDP datagrams sent +.TP +UDP_outErr +UDP datagrams errored on send +.TP +UDP_in +UDP datagrams received +.TP +UDP_inErr +UDP datagrams undeliverable +.TP +UDP_noPort +UDP datagrams received to closed ports +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +udpstat.d will run forever until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/uname-a.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/uname-a.d.1m new file mode 100644 index 000000000000..60d10f700fe7 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/uname-a.d.1m @@ -0,0 +1,35 @@ +.TH uname\-a.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +uname\-a.d \- "uname \-a" demo in DTrace. Uses DTrace. +.SH SYNOPSIS +.B uname\-a.d +.SH DESCRIPTION +This has been written to demonstrate fetching the "uname -a" info +from a DTrace script, which turns out to be all kernel variables. +This is intended as a starting point for other DTrace scripts, by +beginning with familiar statistics. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - uses various kernel symbols. +.SH EXAMPLES +.TP +Print system call counts every second, +# +.B uname\-c.d +.PP +.SH FIELDS +See uname(1) manpage for documentation. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +uname(1), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/vmbypid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/vmbypid.d.1m new file mode 100644 index 000000000000..3c8b8759071a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/vmbypid.d.1m @@ -0,0 +1,50 @@ +.TH vmbypid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +vmbypid.d \- virtual memory stats by PID. Uses DTrace. +.SH SYNOPSIS +.B vmbypid.d +.SH DESCRIPTION +vmbypid.d is a simple DTrace program to print Virtual Memory +statistics by process. + +The virtual memory statistics are documented in the cpu_vminfo struct +in the /usr/include/sys/sysinfo.h file; and also in the vminfo provider +chapter of the DTrace Guide, http://docs.sun.com/db/doc/817-6223. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the vminfo provider. +.SH EXAMPLES +.TP +Sample until Ctrl\-C is hit then print report, +# +.B vmbypid.d +.PP +.SH FIELDS +.TP +EXEC +process name +.TP +PID +process ID +.TP +VM +Virtual Memory statistic +.TP +VALUE +Value by which statistic was incremented +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +vmbypid.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), vmstat(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/vmstat-p.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/vmstat-p.d.1m new file mode 100644 index 000000000000..8198f3d55fee --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/vmstat-p.d.1m @@ -0,0 +1,85 @@ +.TH vmstat-p.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +vmstat-p.d \- vmstat -p demo in DTrace. Uses DTrace. +.SH SYNOPSIS +.B vmstat-p.d +.SH DESCRIPTION +This has been written to demonstrate fetching similar data as vmstat +from DTrace. This program is intended as a starting point for other +DTrace scripts, by beginning with familiar statistics. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - uses various kernel symbols. +.SH EXAMPLES +.TP +Print virtual memory statistics every second, +# +.B vmstat-p.d +.PP +.SH FIELDS +.TP +swap +virtual memory free, Kbytes +.TP +free +free RAM, Kbytes +.TP +re +page reclaims, Kbytes +.TP +mf +minor faults, Kbytes +.TP +sr +scan rate, pages +.TP +epi +executable page ins, Kbytes +.TP +epo +executable page outs, Kbytes +.TP +epf +executable frees, Kbytes +.TP +api +anonymous page ins, Kbytes +.TP +apo +anonymous page outs, Kbytes +.TP +apf +anonymous frees, Kbytes +.TP +fpi +filesystem page ins, Kbytes +.TP +fpo +filesystem page outs, Kbytes +.TP +fpf +filesystem frees, Kbytes +.PP +.SH NOTES +Most of the statistics are in units of kilobytes, unlike the +original vmstat command which sometimes uses page counts. + +As this program does not use Kstat, there is no summary since boot line. + +Free RAM is both free free + cache free. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +vmstat-p.d will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +vmstat(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/vmstat.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/vmstat.d.1m new file mode 100644 index 000000000000..dfbc3605c520 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/vmstat.d.1m @@ -0,0 +1,79 @@ +.TH vmstat.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +vmstat.d \- vmstat demo in DTrace. Uses DTrace. +.SH SYNOPSIS +.B vmstat.d +.SH DESCRIPTION +This has been written to demonstrate fetching the same data as vmstat +from DTrace. This program is intended as a starting point for other +DTrace scripts, by beginning with familiar statistics. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - uses various kernel symbols. +.SH EXAMPLES +.TP +Print virtual memory statistics every second, +# +.B vmstat.d +.PP +.SH FIELDS +.TP +w +swapped out light weight processes +.TP +swap +virtual memory free, Kbytes +.TP +free +free RAM, Kbytes +.TP +re +page reclaims, Kbytes +.TP +mf +minor faults, Kbytes +.TP +pi +page ins, Kbytes +.TP +po +page outs, Kbytes +.TP +fr +pages freed, Kbytes +.TP +sr +scan rate, pages +.TP +in +interrupts, number +.TP +sy +system calls, number +.TP +cs +context switches, number +.PP +.SH NOTES +Most of the statistics are in units of kilobytes, unlike the +original vmstat command which sometimes uses page counts. + +As this program does not use Kstat, there is no summary since boot line. + +Free RAM is both free free + cache free. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +vmstat.d will run until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +vmstat(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/vopstat.1m b/cddl/contrib/dtracetoolkit/Man/man1m/vopstat.1m new file mode 100644 index 000000000000..fa81cc1e9820 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/vopstat.1m @@ -0,0 +1,77 @@ +.TH vopstat 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +vopstat \- vnode interface statistics. Uses DTrace. +.SH SYNOPSIS +.B vopstat [\-t] [/mountname] +.SH DESCRIPTION +This will either produce summary reports of vnode statistics, or +trace activity. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH OPTIONS +.TP +\-t +trace activity as it occurs +.TP +/mountname +examine this FS only +.PP +.SH EXAMPLES +.TP +default output, summary each 5 secs, +# +.B vopstat +.TP +only examine /var, +# +.B vopstat +/var +.TP +trace activity to /var, +# +.B vopstat +\-t /var +.PP +.SH FIELDS +.TP +Count +number of calls +.TP +mSeconds +total of elapsed times +.TP +Event +vop call name +.TP +Device +device instance name +.TP +Path +full pathname to file +.TP +RW +Read or Write +.TP +Size +size in bytes, if available +.TP +Offset +offset in bytes, if available +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +vopstat will sample until Ctrl\-C is hit. +.SH AUTHOR +Richard McDougall +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/weblatency.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/weblatency.d.1m new file mode 100644 index 000000000000..c7ff3d38870a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/weblatency.d.1m @@ -0,0 +1,63 @@ +.TH weblatency.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +weblatency.d \- website latency statistics. Uses DTrace. +.SH SYNOPSIS +.B weblatency.d +.SH DESCRIPTION +This prints statistics for hostnames that browers have set GET requests +for, in particular latency by hostname. + +The latency measured is from the browser sending the GET +request to when the browser begins to recieve the response. It +is an overall response time for the client, and encompasses +connection speed delays, DNS lookups, proxy delays, and web server +response time. + +This is written as an experimental tool, and may not work at all with +your browser. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - depends on browser implementation. +.SH EXAMPLES +.TP +Print report after Ctrl-C is hit, +# +.B weblatency.d +.PP +.SH FIELDS +.TP +HOST +hostname from URL +.TP +NUM +number of GETs +.TP +AVGTIME(ms) +Average time for response, ms +.TP +MAXTIME(ms) +Maximum time for response, ms +.PP +.SH NOTES +See the source code for the "BROWSER" variable, which sets the browser +to trace (currently set to "mozilla-bin"). +.PP +.SH IDEA +Bryan Cantrill (who wrote an elegant version for Sol 10 update 1) +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +weblatency.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/whatexec.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/whatexec.d.1m new file mode 100644 index 000000000000..9c29b8ed5f20 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/whatexec.d.1m @@ -0,0 +1,53 @@ +.TH whatexec.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +whatexec.d \- Examine the type of files exec'd. Uses DTrace. +.SH SYNOPSIS +.B whatexec.d +.SH DESCRIPTION +This prints the first four chacacters of files that are executed. +This traces the kernel function findexec_by_hdr(), which checks for +a known magic number in the file's header. + +The idea came from a demo I heard about from the UK, where a +"blue screen of death" was displayed for "MZ" files (although I +haven't seen the script or the demo). + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - this script uses fbt provider probes which may change for +future updates of the OS, invalidating this script. Please read +Docs/Notes/ALLfbt_notes.txt for further details about these fbt scripts. +.SH EXAMPLES +.TP +Trace execs as they occur, +# +.B whatexec.d +.PP +.SH FIELDS +.TP +PEXEC +parent command name +.TP +EXEC +pathname to file exec'd +.TP +OK +is type runnable, Y/N +.TP +TYPE +first four characters from file +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +whatexec.d will trace until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/woof.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/woof.d.1m new file mode 100644 index 000000000000..212346d6973d --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/woof.d.1m @@ -0,0 +1,46 @@ +.TH woof.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +woof.d \- Bark for new processes. Needs /dev/audio. Uses DTrace. +.SH SYNOPSIS +.B woof.d & +.SH DESCRIPTION +This is an audio alert daemon for process creation. It is a virtual dog which +barks when it sees new processes. If many processes are being created +quickly, it will bark a lot (and become a nuisance - not just the noise, +but also from consuming too much CPU). + +This exists in the DTraceToolkit more for entertainment than +practicality. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the proc provider, /usr/bin/audioplay, and bark.au. +.SH EXAMPLES +.TP +Run the dog, +# +.B woof.d & +.TP +Hear the dog, +$ find /etc -type f -exec grep localhost {} + +.TP +Drive the dog crazy, +$ find /etc -type f -exec grep localhost {} \\; +.PP +.SH NOTES +Beware of the dog! +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +woof.d will exit on Ctrl-C. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +sdtaudiocontrol(1), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/wpm.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/wpm.d.1m new file mode 100644 index 000000000000..8022ae463f50 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/wpm.d.1m @@ -0,0 +1,34 @@ +.TH wpm.d 1m "$Date:: 2007-09-12 #$" "USER COMMANDS" +.SH NAME +wpm.d - Measure words per minute of typing. +.SH SYNOPSIS +.B wpm.d +commandname +eg, +wpm.d bash +wpm.d vim +.SH DESCRIPTION +This script assumes that keystrokes arrive one at a time on STDIN. This +isn't the case for all processes that read keyboard input (eg, sh). +.SH OS +Solaris +.SH STABILITY +stable - Written in DTrace (Solaris 10 3/05). +.SH EXAMPLES +.TP +Default output, +# +.B wpm.d +.PP +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +wpm.d will run until Ctrl-C is hit. +.SH AUTHOR +Brendan Gregg +[CA, USA] +.SH SEE ALSO +dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/writebytes.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/writebytes.d.1m new file mode 100644 index 000000000000..6fb3d85fd08a --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/writebytes.d.1m @@ -0,0 +1,47 @@ +.TH writebytes.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +writebytes.d \- write bytes by process name. Uses DTrace. +.SH SYNOPSIS +.B writebytes.d +.SH DESCRIPTION +writebytes.d is a DTrace OneLiner to a report of the number of +bytes write by process name. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B writebytes.d +.PP +.SH FIELDS +.TP +first field +This is the process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +second field +This is the number of bytes write. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +writebytes.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/writedist.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/writedist.d.1m new file mode 100644 index 000000000000..bdced08f1bca --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/writedist.d.1m @@ -0,0 +1,54 @@ +.TH writedist.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +writedist.d \- write distrib. by process name. Uses DTrace. +.SH SYNOPSIS +.B writedist.d +.SH DESCRIPTION +writedist.d is a DTrace OneLiner to a report the write size and +number of occurrences as a frequency distribution by process name. + +This can be useful to identify the behaviour of processes +that are doing writes. Are they using many small writes, or +fewer large writes. + +Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt +in the DTraceToolkit contain this as a oneliner that can be cut-n-paste +to run. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B writedist.d +.PP +.SH FIELDS +.TP +process name +The process name. There may be several PIDs that have the +same process name, for example with numerous instances of "bash". The +value reported will be the sum of them all. +.TP +value +The size in bytes +.TP +count +The number of occurrences that were at least this size +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +writedist.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +dtrace(1M), truss(1) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/xcallsbypid.d.1m b/cddl/contrib/dtracetoolkit/Man/man1m/xcallsbypid.d.1m new file mode 100644 index 000000000000..173a14f7f71b --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/xcallsbypid.d.1m @@ -0,0 +1,46 @@ +.TH xcallsbypid.d 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +xcallsbypid.d \- CPU cross calls by PID. Uses DTrace. +.SH SYNOPSIS +.B xcallsbypid.d +.SH DESCRIPTION +xcallsbypid.d reports the number of CPU cross calls by process name +and process ID. Cross calls occur when a CPU requests another CPU to +do work on it's behalf. A great number of these can be a burden +on the system. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the sysinfo provider. +.SH EXAMPLES +.TP +This samples until Ctrl\-C is hit. +# +.B xcallsbypid.d +.PP +.SH FIELDS +.TP +PID +process ID +.TP +CMD +process name +.TP +XCALLS +number cross calls +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +xcallsbypid.d will sample until Ctrl\-C is hit. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +mpstat(1m), dtrace(1M) + diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/xvmstat.1m b/cddl/contrib/dtracetoolkit/Man/man1m/xvmstat.1m new file mode 100644 index 000000000000..9f27d959a232 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/xvmstat.1m @@ -0,0 +1,104 @@ +.TH xvmstat 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +xvmstat \- extended vmstat demo in DTrace. Uses DTrace. +.SH SYNOPSIS +.B xvmstat +[interval [count]] +.SH DESCRIPTION +This has been written to demonstrate fetching similar data as vmstat +from DTrace, with a few extra fields. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +unstable - needs various kernel symbols. +.SH EXAMPLES +.TP +Print virtual memory statistics every second, +# +.B xvmstat +.TP +Print every 5 seconds, 6 times, +# +.B xvmstat +5 6 +.PP +.SH FIELDS +.TP +w +swapped out LWPs, number +.TP +swap +virtual memory free, Mb +.TP +free +free RAM, Mb +.TP +re +page reclaims, pages +.TP +maj +major faults, pages +.TP +mf +minor faults, pages +.TP +cow +copy-on-write faults, pages +.TP +pro +protection faults, pages +sr +scan rate, pages +.TP +epi +executable page ins, pages +.TP +epo +executable page outs, pages +.TP +epf +executable frees, pages +.TP +api +anonymous page ins, pages +.TP +apo +anonymous page outs, pages +.TP +apf +anonymous frees, pages +.TP +fpi +filesystem page ins, pages +.TP +fpo +filesystem page outs, pages +.TP +fpf +filesystem frees, pages +.PP +.SH NOTES +Most of the statistics are in units of pages, unlike the +original vmstat command which sometimes uses kilobytes. + +All page values are per second values. + +As this program does not use Kstat, there is no summary since boot line. + +Free RAM is both free free + cache free. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +xvmstat will run until Ctrl\-C is hit, or until the count argument +has been satisfied. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +vmstat(1M), dtrace(1M) diff --git a/cddl/contrib/dtracetoolkit/Man/man1m/zvmstat.1m b/cddl/contrib/dtracetoolkit/Man/man1m/zvmstat.1m new file mode 100644 index 000000000000..cd830e06dba7 --- /dev/null +++ b/cddl/contrib/dtracetoolkit/Man/man1m/zvmstat.1m @@ -0,0 +1,101 @@ +.TH zvmstat 1m "$Date:: 2007-08-05 #$" "USER COMMANDS" +.SH NAME +zvmstat \- print vmstat style info per Zone. Uses DTrace. +.SH SYNOPSIS +.B zvmstat +[\-t] [interval [count]] +.SH DESCRIPTION +This program must be run from the global zone as root. + +Since this uses DTrace, only the root user or users with the +dtrace_kernel privilege can run this command. +.SH OS +Solaris +.SH STABILITY +stable - needs the syscall and vminfo providers. +.SH OPTIONS +.TP +\-t +Print timestamps, string +.TP +interval +Duration for each sample, seconds. default is 1. +.TP +count +Number of samples. default is 1. +.PP +.SH EXAMPLES +.TP +Print virtual memory statistics every second, +# +.B zvmstat +.TP +Print every 5 seconds, 6 times, +# +.B zvmstat +5 6 +.PP +.SH FIELDS +.TP +ZONE +zonename +.TP +re +page reclaims, pages +.TP +mf +minor faults, pages +.TP +fr +pages freed, pages +.TP +sr +scan rate, pages +.TP +epi +executable page ins, pages +.TP +epo +executable page outs, pages +.TP +epf +executable frees, pages +.TP +api +anonymous page ins, pages +.TP +apo +anonymous page outs, pages +.TP +apf +anonymous frees, pages +.TP +fpi +filesystem page ins, pages +.TP +fpo +filesystem page outs, pages +.TP +fpf +filesystem frees, pages +.PP +.SH NOTES +Most of the statistics are in units of pages, unlike the +original vmstat command which sometimes uses kilobytes. + +All page values are a total for the sample duration. + +As this program does not use Kstat, there is no summary since boot line. +.PP +.SH DOCUMENTATION +See the DTraceToolkit for further documentation under the +Docs directory. The DTraceToolkit docs may include full worked +examples with verbose descriptions explaining the output. +.SH EXIT +zvmstat will run until Ctrl\-C is hit, or until the count argument +has been satisfied. +.SH AUTHOR +Brendan Gregg +[Sydney, Australia] +.SH SEE ALSO +vmstat(1M), dtrace(1M) |