If necessary, you can choose to install or uninstall only certain Dr.Web Security Space components by installing or uninstalling the respective packages. Perform custom installation or uninstallation the same way Dr.Web Security Space was installed.
To reinstall a component, you can uninstall it first and then install again.
Installation and uninstallation of Dr.Web Security Space components:
•installed from a universal package.
1. Installation and Uninstallation of Dr.Web Security Space Components Installed from a Repository
If Dr.Web Security Space is installed from a repository, to install or uninstall a component, use a respective command of the package manager of your OS, for example:
1.To remove the Dr.Web Updater component (the drweb-update package) from Dr.Web Security Space installed on CentOS, use the command:
# yum remove drweb-update |
2.To add the Dr.Web Updater component (the drweb-update package) to Dr.Web Security Space installed on Ubuntu, use the command:
# apt-get install drweb-update |
If necessary, use help on the package manager of your OS.
2. Installation and Uninstallation of Dr.Web Security Space Components Installed from a Universal Package
If Dr.Web Security Space is installed from a universal package and you want to additionally install or reinstall a package of a component, you will need an installation file (with the .run extension) that was used to install Dr.Web Security Space. If you do not have this file anymore, download it from the Doctor Web company website.
Unpacking the Installation File
When you start the .run file, you can specify the following command-line parameters:
--noexec—unpack Dr.Web Security Space installation files instead of starting the installation process. The files will be placed in the directory that is specified in the TMPDIR environment variable (usually, /tmp).
--keep—do not delete Dr.Web Security Space installation files and the installation log after the installation.
--target <directory>—unpack Dr.Web Security Space installation files to the specified <directory>.
To get a full list of command-line parameters that can be used with the installation file, run the command:
$ ./<file_name>.run --help |
For custom installation of Dr.Web Security Space components, go to the directory containing the unpacked Dr.Web Security Space package files. If there is no such directory, run the command:
$ ./<file_name>.run --noexec --target <directory> |
As the result, a nested <file_name> directory containing the unpacked Dr.Web Security Space files will appear in the <directory> directory.
Custom Installation of Components
The .run installation file contains packages of all Dr.Web Security Space components (in the RPM format) and auxiliary files. Package files of each component are named as follows:
<component_name>_<version>~linux_<platform>.rpm |
where <version> is a string that contains the version and date of a package release, and <platform> is a platform to run Dr.Web Security Space. Names of all Dr.Web Security Space component packages start with the drweb prefix.
The installation kit includes the zypper package manager intended for the installation of packages. For custom installation, use the installpkg.sh script. To do that, firstly unpack the contents of the installation package to any writeable directory.
|
To install packages, superuser (the root user) privileges are required. To gain superuser privileges, use the su command to change the current user or the sudo command to run the specified command as a different user. |
To install a component package, go to the directory containing the unpacked installation kit and run the following command from the console or from a terminal emulator:
# ./scripts/installpkg.sh <package_name> |
For example:
# ./scripts/installpkg.sh drweb-update |
If it is necessary to install Dr.Web Security Space in full, start the installation script by running the command:
$ ./install.sh |
Furthermore, you can install all Dr.Web Security Space packages (among other things, to install missing or accidentally removed components) by starting the installation of the root meta-package:
# ./scripts/installpkg.sh drweb-workstations |
Custom Uninstallation of Components
If your OS uses RPM packages, to uninstall a package of a component, use the corresponding uninstallation command of the package manager of your OS:
•on Red Hat Enterprise Linux and CentOS, use the yum remove <package_name> command;
•on Fedora, use the yum remove <package_name> or dnf remove <package_name> command;
•on SUSE Linux, use the zypper remove <package_name> command;
•on Mageia or OpenMandriva Lx, use the urpme <package_name> command;
•on ALT, use the apt-get remove <package_name> command.
For example, on Red Hat Enterprise Linux:
# yum remove drweb-update |
If your OS uses DEB packages, use the zypper package manager supplied with Dr.Web Security Space, for the custom uninstallation. To do that, go to the /opt/drweb.com/bin directory and run the command:
# ./zypper rm <package_name> |
For example:
# ./zypper rm drweb-update |
If you want to uninstall Dr.Web Security Space, start the uninstallation script by running the command:
# ./uninst.sh |
To reinstall a component, you can uninstall it first and then install again having started custom or full installation from the installation kit.