DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Troubleshooting system-level problems

Additional help from Technical Support

If you are unable to determine the cause of a system panic, you may want to contact Technical Support for assistance. In addition to the installation checklist and the other configuration information you will be asked to supply in ``Before calling for help'' in the ``Troubleshooting the installation'' chapter of the printed version of the SCO OpenServer Handbook, it is useful to have a memory dump available. To provide this:

  1. Save the memory dump to tape and restore it to disk with the ldsysdump(ADM) command, as discussed in ``Recovering from a system panic''.

  2. Extract the key troubleshooting reports from the dump with a command sequence similar to the following:
       # crash -d /tmp/06May94 -w /tmp/crash.out
       > panic
       > trace
       > user
       > quit
    
    Remember that the ``>'' prompt is generated by the crash command, so do not type them in. This will create the /tmp/crash.out file that contains the output from the panic, trace, and user functions from the crash command.

  3. Print out the /tmp/crash.out file and fax it to your support provider or email the file itself.

Next topic: Common system-wide problems
Previous topic: Studying a panic

© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005