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

vxconfigd also supports the use of syslog to log all of its regular console messages.

When this is enabled, all console output is directed through the syslog interface.

syslog and log file logging can be used together to provide reliable logging to a

private log file, along with distributed logging through syslogd.

Note: syslog logging is enabled by default. Debug message logging is disabled by

default.

If syslog output is enabled, messages with a priority higher than Debug are written

to /var/adm/syslog/syslog.log.

See “Configuring logging in the startup script” on page 62.

Alternatively, you can use the following command to change the debug level:

# vxdctl debug level [pathname]

There are 10 possible levels of debug logging with the values 0 through 9. Level

1 provides the least detail, and 9 the most. Level 0 turns off logging. If a path name

is specified, this file is used to record the debug output instead of the default debug

log file. If the vxdctl debug command is used, the new debug logging level and

debug log file remain in effect until the VxVM configuration daemon, vxconfigd,

is next restarted.

See the vxdctl(1M) manual page.

See the vxconfigd(1M) manual page.

Configuring logging in the startup script

To enable log file or syslog logging on a permanent basis, you can edit the

/sbin/init.d/vxvm-sysboot script that starts the VxVM configuration daemon,

vxconfigd.

Error messages

How error messages are logged