All Dr.Web for UNIX File Servers components keep records about their operation in the logs. You can set a log mode for each component (output of information into the file or to syslog).
You can also select a log verbosity level: for example, set high level of verbosity (the Debug option) or disable logging (the Quiet option). To set the verbosity level, use the LogLevel parameter. You can also specify additional parameters for certain plug-ins to configure their verbosity log level (for example, keeping records of IPC subsystem operation is modified by the IPCLevel parameter).
|
If the LogLevel configuration parameter is not available for a plug-in, it is not allowed to adjust its log mode. In this case, the default log mode has a verbosity level similar to Debug. |
If allowed, you can set one of the following log verbosity levels for a Dr.Web for UNIX File Servers component (the list is arranged in ascending order of detail):
oQuiet – Logging is disabled.
oError – The component logs only fatal errors.
oAlert – The component logs errors and important warnings.
oWarning – The component logs errors and all warnings.
oInfo – The component logs errors, warnings and information messages.
oNotice – This mode is similar to the Info mode, but the component also logs notifications.
oDebug – This mode is similar to the Notice mode, but the component also logs debug information.
oVerbose – The component logs all details on its activity (this mode is not recommended, because a large volume of logged data can considerably reduce performance of both the program and syslog service if it is enabled).
|
Each Dr.Web for UNIX File Servers component can have different set of allowed log verbosity levels. For information on available verbosity levels, see description of the corresponding parameters. |
If you select the mode of logging information into syslog, it is necessary to specify a verbosity log level and a message source label. The label can be used by the syslog service for internal routing of messages to different logs. Routing rules are configured in the syslog daemon configuration file (usually, the path to the file is /etc/syslogd.conf).
To set a flag for syslog messages, specify SyslogFacility parameter value in configuration files. You can specify one of the following parameter values:
oDaemon – label of a resident system service (daemon) message;
oLocal0, ..., Local7 – label of a user application message (8 values are reserved Local0 to Local7);
oKern – label of a system kernel message;
oUser – label of a user process message;
oMail – label of a mail system message.
Note that if information is logged into syslog, an additional parameter - SyslogPriority - can be specified in configuration files. SyslogPriority defines a verbosity level of logging into syslog and is modified by one of the values available for the LogLevel parameter. If you select the mode of logging into the file, SyslogPriority is ignored. Otherwise, information is logged into syslog with the less verbosity level.
Example:
Let us assume that logging of component operation is defined by the following parameter values: LogLevel = Debug, SyslogPriority = Error. If mode of logging into syslog is selected, the log verbosity level is Error (that means only records about errors are to be logged and the Debug value is ignored).