Veritas Volume Manager 5.0.1 Troubleshooting Guide, HP-UX 11i v3, First Edition, November 2009

Most command scripts are not logged, but the command binaries that they call
are logged. Exceptions are the vxdisksetup, vxinstall, and vxdiskunsetup
scripts, which are logged.
If there is an error reading from the settings file, command logging switches to
its built-in default settings. This may mean, for example, that logging remains
enabled after being disabled using vxcmdlog -m off command. If this happens,
use the vxcmdlog utility to recreate the settings file, or restore the file from a
backup.
See the vxcmdlog(1M) manual page.
Transaction logs
The vxtranslog command allows you to log VxVM transactions to a file.
The following examples demonstrate the usage of vxtranslog:
List current settings for transaction logging.vxtranslog -l
Turn on transaction logging.vxtranslog -m on
Set the maximum transaction log file size to 512K.vxtranslog -s 512k
Set the maximum number of historic transaction log
files to 10.
vxtranslog -n 10
Remove any limit on the number of historic transaction
log files.
vxtranslog -n no_limit
Turn on query logging.vxtranslog -q on
Turn off query logging.vxtranslog -q off
Turn off transaction logging.vxtranslog -m off
Transactions are logged to the file, translog, in the directory /etc/vx/log. This
path name is a symbolic link to a directory whose location depends on the operating
system. If required, you can redefine the directory which is linked. If you want to
preserve the settings of the vxtranslog utility, you must also copy the settings
file, .translog, to the new directory.
Warning: The .translog file is a binary and should not be edited.
The size of the transaction log is checked after an entry has been written so the
actual size may be slightly larger than that specified. When the log reaches a
51Logging commands and transactions
Transaction logs