On 2020-08-05, Stuart Henderson <[email protected]> wrote: > On 2020-08-04, Sven F. <[email protected]> wrote: >> Dear readers, >> >> About to upgrade devices, >> the device did not reboot on panic (6.4 stable) >> and i ' d like to see kernel crash in new version >> >> # sysctl -w ddb.panic=1 >> sysctl: ddb.panic: Operation not permitted >> >> wait what ?? >> >> # id >> uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), >> 5(operator), 20(staff), 31(guest) >> >> mkay .. >> >> Is this expected and can be set only early in boot ? >> >> is ddb.panic=0 still supported ? >> >> Thank you for reading . >> >> > > $ man -k any=ddb.console
similar for ddb.panic of course. :) > sysctl(2) - get or set system information > ddb(4) - kernel debugger > pgs(4/macppc) - programmer's switch > sysbutton(4/macppc) - Xserve G4 and G5 front system identifier button > securelevel(7) - securelevel and its effects > boot, boot.conf(8/amd64) - amd64-specific second-stage bootstrap > boot, boot.conf(8/hppa) - hppa-specific bootstrap > boot, boot.conf(8/i386) - i386-specific second-stage bootstrap > boot, boot.conf(8/landisk) - landisk-specific second-stage bootstrap > boot_sparc64(8/sparc64) - sparc64 system bootstrapping procedures > > $ man securelevel > SECURELEVEL(7) Miscellaneous Information Manual SECURELEVEL(7) > > NAME > securelevel – securelevel and its effects > [...] > > >
