SunDiag User's Guide
  Rechercher uniquement dans ce livre
Télécharger cet ouvrage au format PDF

Running Individual SunDiag Tests from the Command Line

5

This chapter describes how to execute individual SunDiag tests from a command line. When running SunDiag tests individually from a command line, change directories to the directory where SunDiag is located.

5.1 Standard Arguments

Every SunDiag test will accept ten standard command arguments. The common line syntax is explained in Table 5-1.
Table 5-1
/opt/SUNWdiag/bin/testname test_specific_arguments [cprquvdt] [h hostname]

Arguments:

testnameThe name of the SunDiag test as it appears in the /opt/SUNWdiag/bin directory.
test_specific_argumentsRefer to the individual test descriptions in "SunDiag Tests"
for test-specific command arguments.
cEnable Core Dump. Creates a core dump file if a system crash happens.
pSingle Pass Only.
rRun On Error. If an error occurs, the test continues with the next test sequence instead of exiting.
Table 5-1
/opt/SUNWdiag/bin/testname test_specific_arguments [cprquvdt] [h hostname]

Arguments:

qQuick Test. Runs a faster, abbreviated version of the test if it exists. Not all tests have a quick option. See the individual test descriptions in the chapters that follow for more details.
uList Usage. Shows how to run the test. It displays three parts: command line usage, standard arguments, and routine specific arguments.
vVerbose Mode. Displays verbose messages regarding the test. These messages tell you more about the testing process. This mode is more valuable for some tests than others; for example, graphics tests only return start and stop messages/failures.
dDebug Mode. Displays debug messages from the test. These messages provide more sophisticated information (mainly for test programmers).
tTrace Mode. Displays messages that enable you to trace down function calls and the sequences being used by the test code.
h hostnameRPC host name. Allows you to specify a separate host name to receive messages regarding this test.

5.1.1 Tests Supported by the Command Line Interface

The following table shows each individual test in the SunDiag exerciser supported by the command line interface and its identification number defined within the SunDiag kernel. For further information about these tests, refer to the individual test descriptions in "SunDiag Tests" or the
"SunDiag User's Guide -- Addendum for SMCC Hardware."
Test Names and ID Numbers
sundiag0probe1
autest2

cdtest4

cg6test6rawtest8
fstest9mono17
fputest12nettest18
newtest19

pmem21sptest23
sunbuttons24sundials25
sunlink26

tapetest28

vmem30pstest31
cg1232bpptest33
lpvitest34

spiftest36mptest37
gttest38fbtest39


audbri41


xbtest43


isdntest45
Table 5-2 Tests Supported by the Command Line Interface

5.2 Running SunDiag Tests - Overview

The following is an overview of the SunDiag testing procedure.
  1. Log into the system under test as superuser and type the appropriate command to start SunDiag (as described in Section 1.4, "Starting the SunDiag Exerciser,").

    Be sure to obtain display permission (server access) using the xhost + hostname command. See Chapter 1, "Introducing the SunDiag System Exerciser," for a list of all software and hardware requirements for running the program.

  2. Display the SunDiag window and check the devices shown in the control panel against the devices you know to be physically present in the system. Section 2.1.4, "Control Panel," if there is a discrepancy.

    Starting the SunDiag exerciser often serves as a quick check for most hardware devices. If you have just installed a device and reconfigured your machine accordingly, the SunDiag test for that device can confirm proper installation.

    Likewise, if the SunDiag environment fails to display a device you know is physically present in your system, there is a problem, and you should recheck your installation carefully.

  3. Choose the global options from the Set SunDiag Options menu.

    These include both testing parameters and scalability options.

    You can create a special global options file. You can load this file before you begin testing, or you can specify the file with the -o option when starting the SunDiag exerciser.

  4. Choose options from the individual test option menus.

    If you want to exercise any different options from those set globally in the Set SunDiag Options menu, click the Options button next to the test name to display individual test option menus. These menus include individual test parameters, test-specific options, and scalability options.

  5. Click the Start Button.

    Or, if you have enabled the Auto Start option from the Set SunDiag Options menu and saved an options file, type sundiag -o options_filename from a command line.