VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Configuring Logging in the Startup Script

38 VERITAS Volume Manager Troubleshooting Guide

There are 9 possible levels of debug logging; 1 provides the least detail, and 9 the most.

To enable syslog logging of console output, specify the option -x syslog to

vxconfigd as shown here:

# vxconfigd [-x [1-9]] -x syslog

Messages with a priority higher than Debug are written to

/var/adm/syslog/syslog.log, and all other messages are written to

/var/adm/configd.log.

If you do not specify a debug level, only Error, Fatal Error, Warning, and Notice messages

are logged. Debug messages are not logged.

Conﬁguring Logging in the Startup Script

To enable log ﬁle or syslog logging, you can edit the following portion of the

/sbin/init.d/vxvm-sysboot script that starts the VxVM conﬁguration daemon,

vxconfigd:

# comment-out or uncomment any of the following lines to enable or

# disable the corresponding feature in vxconfigd.

#opts=”$opts -x syslog” # use syslog for console messages

#opts=”$opts -x log” # messages to vxconfigd.log

#opts=”$opts -x logfile=/foo/bar”# specify an alternate log file

#opts=”$opts -x timestamp” # timestamp console messages

# to turn on debugging console output, uncomment the following line.

# The debug level can be set higher for more output. The highest

# debug level is 9.

#debug=1 # enable debugging console output

Uncomment the lines corresponding to the features that you want enabled at startup. For

example, to setup vxconfigd to use syslog logging, uncomment the opts=”$opts -x

syslog” string.

For more information on logginf options for vxconfigd, refer to the vxconfigd(1M)

manual page.