Thanks Franco.
The issue that's bitten me a couple of times now doing upgrades of Business Edition at a remote office is something triggers a kernel panic on reboot, the firewall drops to KDB and just sits there until someone can physically access the console and restart it.
For a production firewall I would far rather have it auto reboot after 15 seconds
The Kernel Debugging chapter of the handbook says:
In the Glossary it says:
I see DDB and KDB options in the kernel, but not KDB_UNATTENDED.
I'll submit a feature request to add this.
Cheers.
The issue that's bitten me a couple of times now doing upgrades of Business Edition at a remote office is something triggers a kernel panic on reboot, the firewall drops to KDB and just sits there until someone can physically access the console and restart it.
For a production firewall I would far rather have it auto reboot after 15 seconds
The Kernel Debugging chapter of the handbook says:
QuoteThe third way is that any panic condition will branch to DDB if the kernel is configured to use it. For this reason, it is not wise to configure a kernel with DDB for a machine running unattended.
To obtain the unattended functionality, add:
options KDB_UNATTENDED
to the kernel configuration file and rebuild/reinstall.
In the Glossary it says:
Quoteoptions KDB_UNATTENDED: change the default value of the debug.debugger_on_panic sysctl to 0, which controls whether the debugger is entered on panic. When options KDB is not compiled into the kernel, the behavior is to automatically reboot on panic; when it is compiled into the kernel, the default behavior is to drop into the debugger unless options KDB_UNATTENDED is compiled in. If you want to leave the kernel debugger compiled into the kernel but want the system to come back up unless you're on-hand to use the debugger for diagnostics, use this option.
I see DDB and KDB options in the kernel, but not KDB_UNATTENDED.
I'll submit a feature request to add this.
Cheers.
"