HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)

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 asvparutil -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 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.
132 Monitor and Shell Commands