Administrator's Guide

• Files referenced in the command line must both:
— Reside in the inactive system image
— Be referenced in the DRD-safe command by the path relative to the mount point of the
inactive system image
This applies to files referenced as arguments for the -C, -f, -S, -X, and -x logfile options
for an sw command run by drd runcmd and for the update-ux command -f option.
• To use update-ux with a media source or local depot, SWM version A.3.5.1 or later must
be present on the clone.
See drd-runcmd(1M) for further information about restrictions on Software Distributor commands
invoked by drd runcmd.
3.6 Viewing logs
When a drd runcmd operation executes a DRD-safe command, the DRD command runs on the
booted system, and the DRD log, /var/opt/drd/drd.log, is created on the booted system.
However, the DRD-safe command runs on the inactive system image, and its logs (if they exist),
reside on the inactive system image.
Logs can be viewed on the inactive system image by using the drd runcmd view command.
For example, to view the swagent log on the inactive image, execute the following command:
# /opt/drd/bin/drd runcmd view /var/adm/sw/swagent.log
For more information on viewing log files and on maintaining the integrity of system logs, see the
Dynamic Root Disk: Quick Start & Best Practices white paper, located at http://www.hp.com/go/
drd-docs.
20 Updating and maintaining software on the clone