freebsd-nq

History

George V. Neville-Neil 5d06879adb dd DTrace probe points, translators and a corresponding script to provide the TCPDEBUG functionality with pure DTrace. Reviewed by: rwatson MFC after: 2 weeks Sponsored by: Limelight Networks Differential Revision: D3530		2015-09-13 15:50:55 +00:00
..
toolkit	Add META_MODE support.	2015-06-13 19:20:56 +00:00
disklatency	add my scripts to measure io latency per disk...	2014-08-09 20:40:03 +00:00
disklatencycmd	add my scripts to measure io latency per disk...	2014-08-09 20:40:03 +00:00
hotopen	Use dtrace -s instead of /bin/sh for DTrace scripts.	2014-06-26 17:27:36 +00:00
Makefile	Add missing DTrace scripts that exist in the source tree to the Makefile for	2015-06-30 18:23:08 +00:00
nfsattrstats	Update DTrace nfs scripts to track the proper provider names.	2015-09-08 00:30:10 +00:00
nfsclienttime	Update DTrace nfs scripts to track the proper provider names.	2015-09-08 00:30:10 +00:00
README	make the README a bit more clearer...	2014-08-09 20:25:17 +00:00
siftr	Brief demo script showing the various values that can be read via the new SIFTR statically defined tracepoint (SDT).	2015-04-29 18:07:58 +00:00
tcpconn	TCP connection tracker that uses aggregations to show where connections	2015-03-07 19:29:53 +00:00
tcpdebug	dd DTrace probe points, translators and a corresponding script	2015-09-13 15:50:55 +00:00
tcpstate	Summary: Remove the pid printing which does not currently work.	2015-03-08 02:47:38 +00:00
tcptrack	Add a more complex TCP tracking script, which shows connections and	2015-03-07 19:16:09 +00:00
udptrack	Summary: Update the ports to read from the packet rather than the	2015-03-08 04:33:53 +00:00

README

$FreeBSD$

This directory contains scripts for use with the DTrace system.  The
toolkit/ directory installs the latest vendor import of Brendan
Gregg's DTraceToolkit while the other files and directories
contain code generated by the FreeBSD Project for use with DTrace on
FreeBSD.

NOTE: Do not add new scripts to the toolkit directory. New DTraceToolkit
scripts should be send to the maintainer of the toolkit and then brought
back into FreeBSD via future vendor imports.