Page MenuHomeFreeBSD

Update dumpon(8) to include sysctl variable information
AcceptedPublic

Authored by felix.the.red_gmail.com on Oct 24 2021, 5:06 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, May 2, 12:23 PM
Unknown Object (File)
Tue, Apr 30, 4:39 PM
Unknown Object (File)
Fri, Apr 26, 9:43 AM
Unknown Object (File)
Feb 10 2024, 12:58 AM
Unknown Object (File)
Dec 20 2023, 4:21 AM
Unknown Object (File)
Dec 12 2023, 11:45 AM
Unknown Object (File)
Nov 23 2023, 8:07 AM
Unknown Object (File)
Nov 21 2023, 8:10 AM
Subscribers

Details

Reviewers
gbe
Summary

Document debug.minidump, machdep.dump_retry_count, and kern.bootfile sysctl variables.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

gbe added a subscriber: gbe.

LGTM

This revision is now accepted and ready to land.Oct 24 2021, 7:03 AM
markj added inline comments.
sbin/dumpon/dumpon.8
379

kern.bootfile really has nothing to do with dumpon, it is just mentioned in dumpon.8 as part of an example. Several debugging tools, such as kgdb and dtrace use it to find the kernel executable. I think dumpon.8 is not the right place to document it.

kern.bootfile is effectively set by loader(8), together with kern.module_path. I'm not sure where exactly they would best be documented, but IMO it should be grouped with boot loader documentation. We could certainly use better documentation of the handoff between loader and the kernel, I spent a lot of time last weekend trying to figure out how exactly loader(8) picks the kernel to boot (loader.conf variables which control this include kernel, kernel_path, module_path, bootfile, currdev, loaddev, and some are not meant to be set by users), and it's really not clear from our man pages.