Commands: vPars Commands Logging

Beginning with vPars A.03.02, vPars will log the vPars commands executed from the HP-UX shell to the local syslog file (the syslog file of the virtual partition from which the vPars 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 which is sending 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 pid (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:44:30 winona2 vparutil[2947]: user root: vparutil -s 1/0/0/3/1.7.0 -i 7

Oct 29 19:44:30 winona2 vparutil[2947]: exit status 4

Oct 29 19:47:47 winona2 vparmodify[2962]: user root: /sbin/vparmodify -p winona3 -a cpu::1

Oct 29 19:47:47 winona2 vparmodify[2962]: exit status 1

Cases Where No Logging Occurs

Below are the cases where logging does not occur:

a non-root user attempting a vPars command
syntax, usage, or vPars commands version errors
vPars commands which do not change the vPars database and/or do not affect the state of other virtual partitions. These commands include vparstatus, vparextract, vecheck, vpardump, and vparreloc.

Additionally, for only vPars A.03.03 and earlier and A.04.02 and earlier, logging does not occur in these cases as well:

the user replies “no” to vPars commands that request a confirmation before execution
read-only requests, such as vparutil -g (get).

Cases Where Logging Occurs

Below are the cases where logging does occur:

vPars command which change the vPars database and/or affect the state of other virtual partitions.
These commands include vparadmin, vparboot, vparcreate, vparefiutil, vparenv, vparremove, vparmodify, vparreset, and vparutil.

Constraints and Restrictions to Logging

Note the following:

Commands will be logged whether executed on the vPars database in memory, an alternate database, or in standalone mode.
The command line text will be logged on only the partition from which the command was executed. The logging of the command will not be duplicated to the target syslog file (the syslog file of the target virtual partition.
For example, if the vparmodify command is executed from winona1 with the target partition being winona2 (winona1# vparmodify -p winona2 ...), the syslog entries will only appear in the log file of winona1. Nothing will appear in the log file of winona2.
Error messages from the failure of a vpar* command execution are not logged.

Additionally, for only vPars A.03.03 and earlier and A.04.02 and earlier:

When confirmation to execute a vPars command is requested, but the user replies “no”, the vPars command is not logged.

Syslog and Priority and Facility Codes

With the logging, vPars uses LOG_INFO as the priority level and LOG_USER as the facility.




	NOTE: nPartition Logs (see also “nPartition Logs”) On an nPartition server running vPars, all virtual partitions within an nPartition share the same console device: the nPartition’s console. Thus, an nPartition’s console log contains console I/O for multiple virtual partitions. Further, since the vPars Monitor interface is displayed and accessed through the nPartition’s console, vPars Monitor output is also recorded in the nPartition’s console log. There is only one vPars Monitor per nPartition. The server chassis logs record nPartition and server complex hardware events. The chassis logs do not record vPars-related configuration or vPars boot events; however, the chassis logs do record HP-UX "heartbeat" events. The server chassis logs are viewable from the GSPs Show Chassis Log menu. For more information, see the Help within the GSPs online help. The vPars Monitor event logs record only vPars events; it does not contain any nPartition chassis events. For more information, see vparstatus(1M). Also, for a given nPartition, the Virtual Front Panel (VFP) of the nPartition’s console displays an OS heartbeat whenever at least one virtual partition within the nPartition is up.

Commands: vPars Commands Logging

Technical documentation

» Table of Contents

» Glossary

» Index

Log File Location and Log Format

Cases Where No Logging Occurs

Cases Where Logging Occurs

Constraints and Restrictions to Logging

Syslog and Priority and Facility Codes