Commands: Partition Commands Logging; Log File Location And Log Format; Cases Where No Logging Occurs - HP Integrity Superdome 2 16-socket Administrator's Manual

Superdome 2 partitioning administrator guide
Hide thumbs Also See for Integrity Superdome 2 16-socket:
Table of Contents

Advertisement

NOTE:
Run the help command at the OA prompt, to view the current list of Partition Help pages.
The Partition Help pages are:
nPartition Commands
parcreate, parmodify, pardefault, parremove, parstatus, and parperm
vPartition Commands
vparcreate, vparmodify, vparreset, vparremove, vparstatus, vparresources, resourcepath
and vecheck
vparresources and resourcepath are not commands. vparresources provides an overview
of the vPar assignable resources in the complex and resourcepath provides an overview
of the resourcepath specifications for the complex resources in various forms.

Commands: Partition commands logging

On the OA, the Partition commands executed are logged into the OA syslog file. The contents of
the OA syslog file is displayed by show syslog OA at the OA prompt. On the OS side, the
Partition commands executed from the HP-UX shell are logged to the local syslog file (the syslog
file of the partition from which the partition command was executed).

Log file location and log format

The default syslog file on HP-UX systems is/var/adm/syslog/syslog.log.
The format of the log entries is
date hostname vPars_command_name[pid]: user username: vPars_command_line_text
date hostname vPars_command_name[pid]: exit status exit_status
where:
vPars_command_name is the name of the vPars command that sends messages to syslog.
username is the name returned by getlogin(). If no username is given by getlogin(),
the effective username or ID will be used.
vPars_command_line_text is the vPars command line text as typed by the user.
pid is the Process ID of the command invocation. The PIDs shown will be the same for both
the command invocation syslog entry and the exit status syslog entry. This allows matching
the exit status with its corresponding command invocation.
Below are examples of vPars syslog entries.
Oct 29 19:47:47 Oslo2 vparmodify[2962]: user root: /sbin/vparmodify -p Oslo3 -a cpu::1
Oct 29 19:47:47 Oslo2 vparmodify[2962]: exit status 1

Cases where no logging occurs

You can access the syslog file contents using the show syslog OA command from the OA prompt.
Logging does not occur in the following cases (and no changes are made):
A non-root user in an OS attempting a Partition command.
Syntax, usage, or other Partition commands errors.
Commands which do not affect the state of the other partitions such as parstatus,
vparstatus and vecheck.
12
Partitioning in HP Superdome 2

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents