 |
Index for Section 8 |
|
 |
Alphabetical listing for S |
|
sys_check(8)
NAME
sys_check - Generates system configuration information and analysis
SYNOPSIS
/usr/sbin/sys_check [flags ...]
FLAGS
-all
Lists all subsystems, including security information and setld
inventory verification. This command may take a long time to complete.
-allcsc
[Compaq] Used by Unicensus tool to gather information. Includes
security information and the setld scan.
-config
[Compaq] Used by the RCM tool to gather information. Includes only
revision information.
-csc
[Compaq] Used by the Unicensus tool to gather information. Excludes
security information and the setld scan.
-debug
Outputs debugging information.
-dir name
Sets the directory for the frames output. Used only with the -frame
flag. The default is the current directory (.).
-escalate [ n ]
Creates escalation files for reporting problems to Compaq. Produces
two files: TMPDIR/escalate.tar and either TMPDIR/escalate_vmzcore.xx or
TMPDIR/escalate_vmcore.xx.gz. If you use the -escalate flag, sys_check
runs with the -noquick flag and collects the output in the escalate.tar
file. Optionally, you can specify a number with the -escalate flag in
order to define a crash number.
-frame
Produces frame HTML output, which consists of three files:
sys_checkfr.html, sys_checktoc.html, and sys_check.html (unless you
specify a different file name with the -name flag).
-help
Outputs help information.
-name name
Specifies the name to use for the frame files output. The default name
is sys_check.
-nohtml
Produces text output, instead of the default HTML output.
-noquick
Outputs configuration data and the setld scan. Excludes security
information.
-nowarn
Executes only the data gathering pass.
-perf
Outputs only performance data. Excludes configuration data.
-version
Outputs the version of sys_check.
-warn
Executes only the warning pass.
DESCRIPTION
The sys_check command writes to standard output in HTML format the system
configuration (software and hardware) of the running system. The sys_check
command also performs a basic analysis of operating system parameters and
attributes and provides warnings if it detects problems.
The size of the HTML output that is produced by the sys_check command is
usually between .5 MB and 3 MB.
ENVIRONMENT VARIABLES
The following environment variables affect sys_check command execution:
TMPDIR Provides a default location for temporary files. The default is
the /var/tmp directory.
LOGLINES Specifies the number of lines of log file text that sys_check
includes in the HTML output. The default is 500 lines.
BIGNUMFILE
Specifies the number of files in a directory, above which a
directory is considered excessively large. The default is 15
files.
BIGFILE Specifies the file size, above which a file is considered
excessively large. The default is 3072 KB.
VARSIZE Specifies the minimum amount of free space that sys_check requires
in the TMPDIR directory. The default is 15 MB.
RECOVERY_DIR
Specifies the location for the sys_check recovery data. The
default is /var/recovery. The sys_check command automatically
cleans up data from previous command runs. The typical size of
the output generated by each sys_check command run is 400 KB.
This data may be useful in recovering from a catastrophic system
failure.
ADHOC_DIR
Specifies the location at which sys_check expects to find the text
files to include in the HTML output. The default is the
/var/adhoc directory.
TOOLS_DIR
Specifies the location at which sys_check expects to find the
binaries for the tools that it calls. The default is the current
directory.
EXAMPLES
1. The following command creates escalation files that are used to report
problems to Compaq:
sys_check -escalate
2. The following command outputs configuration and performance
information, excluding security information and the setld inventory,
and provides an analysis of common system configuration and
operational problems:
./sys_check > file.html
3. The following command outputs all information, including
configuration, performance, and security information and a setld
inventory of the system:
./sys_check -all > file.html
4. The following command outputs only performance information:
./sys_check -perf > file.html
5. The following command provides HTML output with frames, including
configuration and performance information and the setld inventory of
the system:
./sys_check -frame -noquick
NOTES
You must be root to run the sys_check command.
The sys_check command calls itself recursively. Therefore, the sys_check
must be included in the PATH of the current shell or invoked on the command
line with an explicit path name.
The sys_check command does not change system files.
The sys_check command is updated regularly. Install patches in order to
obtain new versions.
The sys_check command does not perform a total system analysis, but it does
check for the most common system configuration and operational problems on
production systems.
Although the sys_check command gathers firmware and hardware device
revision information, it does not validate this data. This must be done by
qualified support personnel.
FILES
The sys_check command reads many system files.
LIMITATIONS
DECevent or uerf may not be able to read the binary error log file if old
versions of DECevent are being used or if the binary.errlog file is
corrupted. If this problem occurs, install a recent version of DECevent
and, if corrupted, recreate the binary.errlog file.
If you are using HSZ RAID controllers, the hszterm tool is used to query
the status of the controllers.
HSZ controller-specific limitations include the following:
HSZ40 and HSZ50 controllers:
The sys_check command uses a free LUN on each target in order to
communicate with HSZ40 and HSZ50 controllers. To avoid data gathering
irregularities, always leave LUN 7 free on each HSZ SCSI target for
HSZ40 and HSZ50 controllers. Also, ensure that sys_check is not
running simultaneously on multiple cluster nodes.
HSZ70 controller:
The sys_check command uses a CCL port in order to communicate with
HSZ70 controllers. If a CCL port is not available, sys_check will use
an active LUN. To avoid data gathering irregularities, Compaq
recommends that you enable the CCL port for each HSZ70 controller. In
addition, ensure that sys_check is not running simultaneously on
multiple cluster nodes.
The sys_check command attempts to check the NetWorker backup schedule
against the /etc/fstab file. For some versions of Networker, the nsradmin
command contains a bug that prevents sys_check from correctly checking the
schedule. In addition, The sys_check command will not correctly validate
the NetWorker backup schedule for TruCluster services.
EXIT VALUES
The following exit values are returned:
0 Successful completion
>0 An error occurred
RELATED INFORMATION
Unicensus support tool
Revision Configuration Management Tool