Skip to content

Commit 4f2ada0

Browse files
committed
ktrace: Describe CAPFAIL trace point in man page
Update the ktrace(1) man page to describe the recently improved capability failure tracing. Approved by: markj (mentor) Reviewed by: markj MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D44886
1 parent a8acc2b commit 4f2ada0

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

usr.bin/ktrace/ktrace.1

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@
2525
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
2626
.\" SUCH DAMAGE.
2727
.\"
28-
.Dd August 26, 2019
28+
.Dd April 20, 2024
2929
.Dt KTRACE 1
3030
.Os
3131
.Sh NAME
@@ -151,6 +151,21 @@ The
151151
and
152152
.Ar command
153153
options are mutually exclusive.
154+
.Sh CAPABILITY VIOLATION TRACING
155+
When the
156+
.Cm p
157+
trace point is specified,
158+
.Nm
159+
will record
160+
.Xr capsicum 4
161+
capability mode violations made by the traced process.
162+
Violations will be logged regardless of whether the process has actually
163+
entered capability mode.
164+
.Pp
165+
For developers that are interested in Capsicumizing their programs, the
166+
.Cm c , n , p
167+
trace points can help quickly identify any system calls and path lookups that
168+
are triggering violations.
154169
.Sh EXAMPLES
155170
Run "make", then trace it and any child processes:
156171
.Dl $ ktrace -i make
@@ -183,7 +198,8 @@ Disable tracing of all user-owned processes:
183198
.Xr kdump 1 ,
184199
.Xr truss 1 ,
185200
.Xr ktrace 2 ,
186-
.Xr utrace 2
201+
.Xr utrace 2 ,
202+
.Xr capsicum 4
187203
.Sh HISTORY
188204
The
189205
.Nm

0 commit comments

Comments
 (0)