Operating Principles

The component is designed to establish connections to Doctor Web update servers to check for updates for virus databases and anti-virus engine Dr.Web Virus-Finding Engine . The lists of servers which constitute an available update zone are stored in a special file (the file is signed to prevent modification).

If the product is not connected to the central protection server or it is connected to the server in mobile mode, Dr.Web Updater is automatically started by the Dr.Web ConfigD configuration daemon. Startup is performed at periods specified in the settings. The component can be also started by the configuration daemon if the appropriate command is received from a user (unscheduled update). The component operation scheme is shown in the figure below.

Figure 19. Diagram of the components’ operation

When updates become available on the servers, they are downloaded to the <var_dir>/cache directory (for Linux—var/opt/drweb.com/cache), after that they are moved to the working directories of Dr.Web for UNIX File Servers.

By default, all updates are performed from the updating zone which is common for all Dr.Web products. The list of the servers used by default, which are included to the updating zone, is specified in the files which are located in directories, defined in *DrlDir