Starting the Autonomous Instance

Dr.Web Security Space can be run in special mode—as an autonomous instance.

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

Aspects of the Dr.Web Security Space graphical management interface running as an autonomous instance:

•To run the Dr.Web Security Space graphical management interface as an autonomous instance, you will need a valid key file, operation in centralized protection mode is not supported (it is possible to install the key file exported from a centralized protection server). In this case, even if Dr.Web Security Space is connected to the centralized protection server, the autonomous instance does not notify the centralized protection server of the threats detected in the autonomous instance 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 used for interaction of components are created only in a directory with an unique name, which is created when the autonomous instance is started. The unique temporary directory is created in the directory for temporary files (specified by the TMPDIR environment variable).

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

•All the required paths (to virus databases, scanning engine and executable files of service components) are set to default values or retrieved from custom 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.