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 , and possibly, database of web resource categories and the anti-spam component (depending on the installed product). 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.

— Dr.Web for UNIX as a whole and external Dr.Web applications together with systems which are not included in the solution.

— external to Dr.Web for UNIX programs and products for its integration.

— Components that are included in Dr.Web for UNIX engine. Other product components use the engine as a service that performs anti-virus checks.

— Service components designed to perform particular anti-virus protection functions (for example, scanning file system objects, updating virus databases, managing the operation of the product).

— Components that provide the user with the interface for Dr.Web for UNIX.

— Quarantine as a set of file system directories which store isolated malicious files.

Components marked with a dashed line can be missing depending on the distribution.

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.

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 update.drl. If necessary, a special updating zone can be created (different for every updated component) at a client request, the list of the servers for this zone is specified in a separate file (by default, under the name custom.drl). In this case the update component will receive updates only from these components, without using servers from the default zone.

If you do not want to use the special updating zone, clear the *CustomPath value of the corresponding parameter in the component settings.

The content of the files with server lists is signed, so that the files cannot be modified. If you need to create a special list of update servers, contact technical support.

The component can back up the updated files for the next rollback of the updates, performed at user request. You can specify the location and the detail level of the backed up files in the settings. To roll back updates, use the command-line tool for Dr.Web for UNIX for managing the solution from the Dr.Web Ctl command line (it is run by drweb-ctl command).