Solaris

It is supposed to stop the machine from rebooting. Yes.
I'm merely indicating that it does not work consistently - most specifically when there is an intermittent hardware issue. ie: no core dump / simply goes from running to rebooting.

it works for me... and as far as i can see it works as designed. if you've problem with that, you should maybe open a call at sun and get the problem fixed...

good luck...

Hi
I wonder if maybe it´s a good practice to store the OK variables in a text file
for futures references.

into OS should you use the eeprom command

root@ultra # eeprom
asr-policy=normal
test-args: data not available.
diag-passes=1
local-mac-address?=true
fcode-debug?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
output-device=screen
input-device=keyboard
auto-boot-on-error?=false
error-reset-recovery=sync
load-base=16384
auto-boot?=true
network-boot-arguments: data not available.
boot-command=boot
diag-file: data not available.
diag-device=disk net
boot-file: data not available.
boot-device=disk net
use-nvramrc?=false
nvramrc=." ChassisSerialNumber ######### " cr
security-mode=none
security-password: data not available.
security-#badlogins=0
verbosity=min
diag-trigger=none
service-mode?=false
diag-script=none
diag-level=max
diag-switch?=false

yes, its a good practice to. In case you set-defaults whilst troubleshooting, you will know howto set it back to origin, if required.