Running Dr.Web Daemon

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

•Search and load of the configuration file. If the configuration file is not found, loading of Dr.Web Daemon terminates. Path to the configuration file can be specified on startup with the -ini command line parameter: {path/to/your/drweb32.ini}, otherwise, the default value (%etc_dir/drweb32.ini) can be used. On startup, correctness of several configuration parameters is checked, and if a parameter value is incorrect, the default parameter value is set;

•Creation of a log file. A user account under which Dr.Web Daemon is started must have appropriate privileges to write to the log file directory. Users do not have write permission for the default log directory (/var/log/). Therefore, if the User parameter is specified, adjust the LogFileName parameter and provide alternative log file directory;

•Load of a key file from the location specified in the configuration file. If the key file is not found, loading of Dr.Web Daemon terminates;

•If the User parameter is specified, Dr.Web Daemon attempts to change its privileges;

•Load of Dr.Web Engine (drweb32.dll). If Dr.Web Engine is damaged or not found (because of errors in the configuration file), initialization of Dr.Web Daemon terminates;

•Load of virus databases in arbitrary sequence from the location specified in the configuration file. If virus databases are damaged or absent, initialization of Dr.Web Daemon proceeds;

•Dr.Web Daemon enters daemon mode, so all information about initialization problems cannot be output to the console and is logged to the log file;

•Creation of a socket for interaction between Dr.Web Daemon and other Dr.Web for UNIX File Servers modules. When TCP-sockets are used, there can be several connections (loading continues if at least one connection is established). When a UNIX socket is used, Dr.Web Daemon user account must have appropriate privileges to read and write from the directory of this socket. User accounts for modules must have execution access to the directory and write and read access to the socket file. Users do not have write permission for the default socket directory (/var/run/). If the User parameter is specified, adjust the Socket parameter and provide alternative path to the socket file. If creation of the UNIX socket was unsuccessful, initialization of Dr.Web Daemon terminates;

•Creation of a PID file with Dr.Web Daemon PID information and transport addresses. User account under which Dr.Web Daemon is started must have appropriate privileges to write to the directory of the PID file. Users do not have write permission for the default socket directory (/var/run/). So, if the User parameter is specified, adjust the PidFile parameter and provide alternative path to the PID file. If creation of the PID file was unsuccessful, initialization of Dr.Web Daemon terminates.