Starting Standalone Instance

Dr.Web Security Space can be run in special mode—as a standalone instance.

If the graphical management interface of Dr.Web Security Space is run in standalone instance mode, 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 in standalone instance mode:

•To run the Dr.Web Security Space graphical management interface in standalone instance mode, 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 standalone instance does not notify the centralized protection server of the threats detected in standalone instance mode.

•All additional components that manage the operation of the standalone instance of the graphical management interface, will be started on behalf of the current user and will work with a specifically generated configuration file.

•All temporary files and Unix sockets used for interaction of components are created only in a directory with a unique name, which is created when the standalone instance is started. The unique temporary directory is created in the directory for temporary files (specified by the TMPDIR environment variable).

•The standalone 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 standalone instances of the graphical management interface is unlimited.

•When the standalone instance of the graphical management interface is shut down, the set of the servicing components that manages its operation is also shut down.