Starting the Autonomous Copy

Dr.Web for Linux supports running in a special mode—as an autonomous copy.

If the graphical management interface of Dr.Web for Linux is run as autonomous copy, then it will work with a separate set of service components (background working configuration daemon of Dr.Web for Linux (drweb-configd), Scanner and the scan engine), run for supporting the running instance of the software.

Features of the Dr.Web for Linux graphical management interface run as an autonomous copy:

•To run the Dr.Web for Linux graphical user interface as an autonomous copy, you will need a valid key file. Working in the centralized protection mode is not supported (you can install the key file, exported from the centralized protection server). In this case, even if Dr.Web for Linux is connected to the centralized protection server, the autonomous copy does not notify the centralized protection server of the threats detected in the autonomous copy mode.

•All additional components that are run to serve the work of the autonomous copy of the graphical management interface, will be launched as the current user and will work with a configuration file, separately generated for this session.

•All temporary files and UNIX sockets are created only in the directory with an unique name, which is created when the autonomous copy is launched. The unique temporary directory is created in the system directory for temporary files (path to this directory is available in the TMPDIR environment variable).

•The autonomous copy of the graphical management interface does not launch SpIDer Guard and SpIDer Gate monitors, only files scanning and quarantine management functions, supported by Scanner, are available.

•All the required paths (to virus databases, scan engine and executable files of the service components) are defined by default or retrieved from the special environment variables.

•The number of simultaneously running autonomous copies of the graphical management interface is unlimited.

•When the autonomous copy of the graphical management interface is shut down, the set of servicing components is also terminated.