Running Dr.Web Monitor        

When Dr.Web Monitor is started with the default settings, the following actions are performed:

1.Dr.Web Monitor searches for and loads its configuration file. If the configuration file is not found, loading process stops;

2.Dr.Web Monitor starts operating in the daemon mode. So, information about loading problems cannot be output to the console and, thus, is logged to the file;

3.Socket for Dr.Web Monitor interaction with other Dr.Web for Novell Storage Services modules is created. If a TCP socket is used, several connections can be established (loading process continues if at least one connection is established). If a UNIX socket is used, it can be created only if the user whose privileges are used to run drweb-monitor has read and write access to the certain directory. If a socket cannot be created, loading process stops;

4.PID-file with information on drweb-monitor process identifier is created. If the PID-file cannot be created, loading process stops;

5.drweb-monitor module starts other suite components. If a module cannot load, Dr.Web Monitor tries to restart it. If all Dr.Web Monitor attempts to start the module failed, Dr.Web Monitor unloads all previously loaded modules and terminates. Dr.Web Monitor reports problems connected with the modules startup in one of the available ways (logging to the file, notifying via email, startup of a custom program). Notification methods used for various modules are set in the Dr.Web Monitor meta-configuration file (.mmc).

To start Dr.Web Monitor in the automatic mode, do one of the following:

•change the value of the ENABLE variable to 1 in the drweb-monitor enable file .