Sir Coppa,
That's why I apologized... Forgetting the possibility of reading out the
value of ddb.panic. Kind of stupid for a person (me) doing 'sysctl
hw.sensors' 10 times a week. But that's off topic.
It is set now and returns 0. That machine will me moved 30 kilometers
away and must stay up for a month or two. I think 'ddb.panic=0' is the
right thing to set on that machine.
Thanks to you, Sir Coppa, and also to Sir Edigarov who replied also,
Kind regards,
Frank ter Voorde
On 06/22/11 15:21, David Coppa wrote:
On Wed, 22 Jun 2011, ter Voorde Informatiesystemen wrote:
In /etc/sysctl.conf I see the following commented line:
#ddb.panic=0
and nothing else about ddb.panic is present there. With other words,
I guess: 'ddb.panic=0' is the default boot time setting and does not
have to be set explicitly.
I now suppose: on a kernel panic, this system will not drop into ddb
(kind-of waiting for someone to retrieve useful information about
the panic) and is most likely to reboot. Is that correct?
Exactly the opposite:
$ sysctl ddb.panic
ddb.panic=1
You need to uncomment that line in /etc/sysctl.conf.
Cheers,
David
