The process-specific-trace information file, The process-specific-trace information file -193 – HP XP P9500 Storage User Manual
Page 261

view, completion time = yyyy/mm/dd hh:mm:ss
#
After you have set up the collection of audit log data, use the following
command to make sure that the setting has been specified correctly:
# /opt/DynamicLinkManager/bin/dlnkmgr view -sys -audlog
Audit Log : on(6)
Audit Log Category : all
Audit Log Facility : local0
KAPL01001-I The HDLM command completed normally. Operation name =
view, completion time = yyyy/mm/dd hh:mm:ss
#
The Process-specific-trace Information File
When HDLM is used, the dlnkmgr command logs are output to the following
process-specific-trace (traces for multiple processes) information files of
Hitachi Network Objectplaza Trace Library (HNTRLib2): /var/opt/
DynamicLinkManager/log/dlnkmgrn.log (n indicates a file number).
Table 3-63 Setting Values for the Process-specific-trace Information Files on
shows the setting values for the process-specific-trace
information files:
Table 3-63 Setting Values for the Process-specific-trace Information Files
Settings
Values
#
Size of the process-specific-trace information file
2048 (KB)
Number of process-specific-trace information files
2
#
The setting values cannot be modified.
Notes on Using the Hitachi Network Objectplaza Trace Library
Note the following when using Hitachi Network Objectplaza trace library:
•
If a different Hitachi product is using HNTRLib2 when you attempt to
uninstall HDLM, HNTRLib2 will not be uninstalled
Creating a Character-Type Device File for an HDLM Device
This section describes how to create a character-type device file for an HDLM
device.
•
HDLM creates only a block-type device under /dev.
•
If the OS is Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6, use
an udev rule file to create the character-type device file. If the OS is Red
Creating an HDLM Environment
3-193
Hitachi Dynamic Link Manager User Guide (for Linux(R))