Page MenuHomeFreeBSD

ktrace: Describe CAPFAIL trace point in man page
ClosedPublic

Authored by jfree on Apr 20 2024, 5:44 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 29, 12:23 AM
Unknown Object (File)
Mon, Nov 18, 3:41 AM
Unknown Object (File)
Mon, Nov 18, 3:25 AM
Unknown Object (File)
Mon, Nov 18, 1:47 AM
Unknown Object (File)
Sep 15 2024, 12:15 AM
Unknown Object (File)
Sep 12 2024, 6:23 AM
Unknown Object (File)
Sep 4 2024, 3:44 AM
Unknown Object (File)
Sep 3 2024, 7:09 AM
Subscribers

Details

Summary

Update the ktrace(1) man page to describe the recently improved
capability failure tracing.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jfree requested review of this revision.Apr 20 2024, 5:44 PM
usr.bin/ktrace/ktrace.1
159

You should reference capsicum.4 here somehow.

161

This wording is a bit confusing to me: I think it could be simplified with something like, "Violations are logged regardless of whether the process has actually entered capability mode."

165

Maybe note that it's more useful when combined with "c".

167

Well, the number of log entries is a pretty weak indicator.

jfree marked 4 inline comments as done.

Address Mark's comments

This revision is now accepted and ready to land.Apr 22 2024, 1:26 PM