HP Integrity Superdome 2 16-socket HP Superdome 2 Partitioning Administrator G - Page 15

Commands: Partition Commands Logging, Log File Location and Log Format, Cases Where No Logging Occurs

Get HP Integrity Superdome 2 16-socket PDF manuals and user guides View all HP Integrity Superdome 2 16-socket manuals
Add to My Manuals
Save this manual to your list of manuals

Page 15 highlights

Note the following on Partition help pages: - You can run the help command to see the current list of Partition help pages. - As of this printing, the Partition help pages are: ◦ nPartition Commands parcreate, ,parmodify, pardefault, parremove, parstatus, and parperm ◦ vPartition Commands vparcreate, , vparmodify, vparreset, vparremove, vparstatus, and vecheck 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 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: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 On the OA, the syslog file contents is accessed by show syslog OA from the OA prompt. Below are the cases where logging does not occur (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. Commands: Partition Commands Logging 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
Note the following on Partition help pages:
—
You can run the
help
command to see the current list of Partition help pages.
—
As of this printing, the Partition help pages are:
◦
nPartition Commands
parcreate
,,
parmodify
,
pardefault
,
parremove
,
parstatus
, and
parperm
◦
vPartition Commands
vparcreate
,,
vparmodify
,
vparreset
,
vparremove
,
vparstatus
, and
vecheck
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 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: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
On the OA, the syslog file contents is accessed by
show syslog OA
from the OA prompt.
Below are the cases where logging does
not
occur (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
.
Commands: Partition Commands Logging
15