Installing and Managing HP-UX Virtual Partitions (includes A.04.01)

Monitor and Shell Commands
Commands: vPars Commands Logging
Chapter 5
109
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 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
• the user replies “no” to vPars commands that request a confirmation before execution
• 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, read-only requests, such as vparutil -g (get), will not be logged.
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 vparboot, vparcreate, vparremove, vparmodify, vparreset, and vparutil.