Veritas InfoScale™ 7.3.1 Troubleshooting Guide - Solaris

To configure logging in the startup script

1. 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

   The opts="$opts -x syslog" string is usually uncommented so that vxconfigd uses syslog logging by default. Inserting a # character at the beginning of the line turns off syslog logging for vxconfigd.

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

   By default, vxconfigd is started at boot time with the -x syslog option. This redirects vxconfigd console messages to syslog. If you want to retain this behavior when restarting vxconfigd from the command line, include the -x syslog argument, as restarting vxconfigd does not preserve the option settings with which it was previously running. Similarly, any Veritas Volume Manager operations that require vxconfigd to be restarted may not retain the behavior that was previously specified by option settings.

2. After making changes to the way vxconfigd is invoked in the startup file, run the following command on a Solaris 11 system to notify that the service configuration has been changed:

   # svcadm refresh vxvm/vxvm-sysboot