51 lines
1.4 KiB
Plaintext
51 lines
1.4 KiB
Plaintext
.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)
|
|
|