Lenore,

You might want to go to this site: http://www.beechglen.com/ and look at
their PRESHUT command file. You may find that it is better to check things
out PRIOR to shutting a system down rather than after the system has come
back up. I have used this command file quite a bit and it has saved me one
than once especially for un-validated NMCONFIG files.

Jim

[log in to unmask] wrote in message
<[log in to unmask]>...
>I'm looking for ideas on what kinds of check off lists/verification steps
>others may have after doing a system reboot to verify basic system
>processes are functional. We currently have nothing formal in place and
>after a recent disaster (nmmgr was not verified the last time someone went
>into it and when the system was reboot, the DTC devices couldn't be found
>and the technology staff had egg on its' face because we assumed all was
>ok and went home for the night...), I am thinking that it's not a bad idea
>to implement something!
>
>My list so far has things like verify the lan, verify logging is running,
>print to a DTC device, print to a networked device, and review
>job/session/outfence settings.
>
>Are there other basic system processes that can be included? The good
>thing is that we rarely need to reboot, usually only when we're doing some
>kind of upgrade. Because of the great stability of the system, we seem to
>be getting complacent when we do have to restart the system.
>
>TIA and TGIF!!!
>
>Lenore Siemsen
>Technology Support Services Manager
>St. Paul Pioneer Press
>[log in to unmask]
>651-228-5077
>
>**********
>Posted from www.3kworld.com
>