You can set individual log levels for each resource detector from the command line and the RMS Wizard Tools.
Note
To enable detector logging, the RMS base monitor log level must include level 2 (detector tracing), regardless of the individual detector log level settings. By default, the base monitor log level is off, so detector logging is suppressed. See "F.4 Managing base monitor log output".
If RMS is already running, you can use the following commands to manage the detector log level:
hvutil -L display <resource> hvutil -L <level> <resource>
The first hvutil command displays the current detector log level for the indicated resource, and the second form of the command sets the log level:
<level> can be either 0 (zero) to turn off logging for the resource, or a positive number to turn on logging at that level.
<resource> is the name of the resource monitored by the detector. This must be a generic resource, i.e., it must be an object of type gResource. You can find these in the 'hvdisp -a' output.
The current log level remains in effect until another 'hvutil -L' command changes the log level, 'hvutil -l off' is issued, or until RMS is shut down.
The valid range of log levels is 1 to 9, and the default value is 1. The log level can be modified from the hvw command as follows:
Select the Configuration-Edit-Global-Settings menu.
Choose the DetectorDetails sub-menu. The following screen is displayed.
Figure F.1 Wizard Tools Detector Details menu
Select MemoryLogLevel and change the value to the desired level. The log level applies to all detectors.
Changing the log level while running RMS
It is possible to turn debug reporting on or off dynamically from the RMS Wizard detectors by using the hvw command as follows:
Select Configuration-Edit-Global-Settings.
Choose the DetectorDetails sub-menu.
Select the DynamicDetectorLogging menu item.
The default value is 0, which turns off debugging. Values in the range 1 to 9 turn on debugging, and higher numbers produce more information. The volume of generated log messages varies according to the detector, so a high value for one detector may produce fewer messages than a low value for another. Changes to this value do not take effect until the next time the configuration is activated.
Using hvw to turn on dynamic logging actually creates the file <RELIANT_PATH>/etc/wizardloglevel, which simply contains the desired debug level as a single-digit ASCII number. You can bypass the hvw command and create (or delete) the wizardloglevel file manually, as long as you observe the following rules:
If the file does not exist, or If the file contains the number 0 (zero), then debugging is turned off.
If the file exists but is empty, a value of 3 is assumed.
If the file contains a value in the range 1 to 9, debugging is turned on.
Note
Turning on debugging should only be done when problems occur. Once the problems are resolved, debugging should be turned off to avoid filling the file system with extraneous information.
