On 2020-08-05, Stuart Henderson wrote:
> On 2020-08-04, Sven F. 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 permit
On 2020-08-04, Sven F. 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(
On Tue, Aug 4, 2020 at 7:25 PM Philip Guenther wrote:
>
> On Tue, Aug 4, 2020 at 12:23 PM Sven F. wrote:
> ...
>>
>> # sysctl -w ddb.panic=1
>> sysctl: ddb.panic: Operation not permitted
>
> ...
>>
>> Is this expected and can be set only early in boot ?
>
>
> Yes, exactly. Read the securelevel(
On Tue, Aug 4, 2020 at 12:23 PM Sven F. wrote:
...
> # sysctl -w ddb.panic=1
> sysctl: ddb.panic: Operation not permitted
...
> Is this expected and can be set only early in boot ?
>
Yes, exactly. Read the securelevel(7) or sysctl(2) manpages for details.
> is ddb.panic=0 still supported
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(op
5 matches
Mail list logo