User`s guide

SGI Media Server Crash Files
007-4403-003 105
4. Reset the SystemPartition, OSLoadPartition, and root environment
variables to the values of the disk partition that contains the alternate plex and the
swap environment variable to have the value of the alternate swap partition. For
example:
>> setenv SystemPartition dksc(0,2,8)
>> setenv OSLoadPartition dksc(0,2,0)
>> setenv root dks0d2s0
>> setenv swap /dev/dsk/dks0d2s1
5. Exit the Command Monitor and restart the system:
>> exit
...
Option? 1
Starting up the system...
...
It is beyond the scope of this book to describe the intricacies of the IRIX filesystem
features and tools that provide optimal performance for the SGI Media Server. For
detailed information, see the latest version of IRIX Admin: Disks and Filesystems.
SGI Media Server Crash Files
Inside the /usr/vtr/adm/crash directory is a subdirectory for each program that
crashes. If a program crashes, a directory is dynamically created with that program
name. Inside that directory a core file is created containing the crash information.
When the SGI Media Server detects a program crash, it renames the core file to
core.number, where number is the next incremental number. This scheme prevents core
files from overwriting each other.
SGI Media Server crash files are saved to aid SGI support personnel in diagnosing server
software errors. Since core files may be periodically purged, generate a stack trace for the
crash files to capture the pertinent information. Use the following procedure to generate
a stack trace:
1. Log in to the SGI Media Server as root.
2. Change the directory to the appropriate core file location, as shown in the following:
server 1# cd /usr/vtr/adm/crash/vvtr/core.number
The value number is the core file directory of interest.