1
0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-26 11:47:31 +00:00
freebsd/share/dtrace
Simon J. Gerraty ccfb965433 Add META_MODE support.
Off by default, build behaves normally.
WITH_META_MODE we get auto objdir creation, the ability to
start build from anywhere in the tree.

Still need to add real targets under targets/ to build packages.

Differential Revision:       D2796
Reviewed by: brooks imp
2015-06-13 19:20:56 +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 udp track shows UDP data as it arrives and leaves the system 2015-03-08 04:29:41 +00:00
nfsattrstats Use dtrace -s instead of /bin/sh for DTrace scripts. 2014-06-26 17:27:36 +00:00
nfsclienttime Use dtrace -s instead of /bin/sh for DTrace scripts. 2014-06-26 17:27:36 +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
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

$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.