FR> Because the server didn't stop. It caught the crash,
FR> notified everyone on the server that a critical error had
FR> occurred and the server would be restarted in 2 minutes,
FR> waited 2 minutes, then rebooted itself.
RA> Is something like this (for instance, after an abend) also
RA> possible with NetWare 4.1?
No, new feature with 4.11. Reason enough to upgrade to 4.11. Minimizing
downtime.
RA> Or: how can I make the server reboot again in case of an
RA> abend, leaving a message in an errorlog?
Pre 4.11, no what that I'm aware of. Easier to prevent the crash than try to
recover automatically from it.
4.11 appends the crash message to an audit log, first on the C drive, then
copied to SYS once the server has rebooted. This should handle cases where
SYS goes into the weeds.
framsey@goodyear.com; frank.ramsey@fallsbbs.com - CNE, CNA-4, PE
--- EZPoint V2.2
---------------
* Origin: -- A Point on Pine Lake (330)-796-3146 -- (1:157/603.70)
|