Custom Installation and Uninstallation of Components

In this section

•Typical Component Sets for Custom Installation

•Installation and Uninstallation of Dr.Web Mail Security Suite Components Installed from a Repository

• Installation and Uninstallation of Dr.Web Mail Security Suite Components Installed from a Universal Package

oUnpacking the Installation File

oCustom Installation of Components

oCustom Uninstallation of Components

If necessary, you can choose to install or uninstall only certain Dr.Web Mail Security Suite components by installing or uninstalling the respective packages. Perform custom installation or uninstallation the same way Dr.Web Mail Security Suite was installed.

To reinstall a component, you can uninstall it first and then install again.

Typical Component Sets for Custom Installation

If you need to install Dr.Web Mail Security Suite with limited functionality, you can install only component packages that provide the necessary functionality instead of installing a root meta-package from the repository or from the universal package. The packages required to resolve dependencies will be automatically installed. The table below displays component sets designed to resolve typical Dr.Web Mail Security Suite tasks. The Packages for Installation column lists packages required for installation to obtain the specified component set.

Custom Component Set

Packages for Installation

To Be Installed

Minimal set for console scanning

•drweb-filecheck,

•drweb-se

•Dr.Web ConfigD,

•Dr.Web Ctl,

•Dr.Web File Checker,

•Dr.Web Scanning Engine,

•Dr.Web Updater,

•Virus databases

Set for ClamAV emulation (clamd)

•drweb-clamd,

•drweb-se

•Dr.Web ClamD,

•Dr.Web ConfigD,

•Dr.Web Ctl,

•Dr.Web File Checker,

•Dr.Web Network Checker,

•Dr.Web Scanning Engine,

•Dr.Web Updater,

•Virus databases

Set for scanning email messages as a filter that can be connected to an MTA

If anti-virus scanning of email messages is not needed, drweb-netcheck and drweb-se packages are optional.
If anti-virus scanning is to be performed on another server, which will receive data for scanning via Dr.Web Network Checker, the drweb-se package is optional.
If there is no need to check whether a URL from email messages belongs to a category of unwanted web resources, the drweb-dws package is optional.
If there is no need to scan email messages for spam, the drweb-antispam and drweb-vaderetro packages are optional.

•drweb-antispam,

•drweb-dws,

•drweb-maild,

•drweb-netcheck,

•drweb-se,

•drweb-vaderetro

•Dr.Web ASE, ****

•Dr.Web ConfigD,

•Dr.Web Ctl,

•Dr.Web MailD,

•Dr.Web Network Checker,

•Dr.Web Scanning Engine, *

•Dr.Web Updater, ***

•Dr.Web URL Checker,

•Database of web resource categories, **

•Virus databases, *

•Spam filter ****

Set for scanning email messages in the transparent proxy mode via the SMTP, POP3, and IMAP

If anti-virus scanning of email messages is not needed, drweb-netcheck and drweb-se packages are optional.
If anti-virus scanning is to be performed on another server, which will receive data for scanning via Dr.Web Network Checker, the drweb-se package is optional.
If there is no need to check whether a URL from email messages belongs to a category of unwanted web resources, the drweb-dws package is optional.
If there is no need to scan email messages for spam, the drweb-antispam and drweb-vaderetro packages are optional.

•drweb-antispam,

•drweb-dws,

•drweb-firewall,

•drweb-gated,

•drweb-maild,

•drweb-netcheck,

•drweb-se,

•drweb-vaderetro

•Dr.Web ASE, ****

•Dr.Web ConfigD,

•Dr.Web Ctl,

•Dr.Web Firewall for Linux,

•Dr.Web MailD,

•Dr.Web Network Checker,

•Dr.Web Scanning Engine, *

•Dr.Web Updater, ***

•Dr.Web URL Checker,

•SpIDer Gate,

•Database of web resource categories, **

•Virus databases, *

•Spam filter ****

* The component will not be installed if the package drweb-se is not installed.
** The component will not be installed if the package drweb-dws is not installed.
*** The Dr.Web Updater component will be installed only if virus databases, the database of web resource categories, or the spam filter are installed.
**** The component will not be installed if packages for scanning for spam are not installed.

Installation and Uninstallation of Dr.Web Mail Security Suite Components Installed from a Repository

If Dr.Web Mail Security Suite 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 Network Checker component (the drweb-netcheck package) from Dr.Web Mail Security Suite installed on CentOS, use the command:

# yum remove drweb-netcheck

2.To add the Dr.Web Network Checker component (the drweb-netcheck package) to Dr.Web Mail Security Suite installed on Ubuntu, use the command:

# apt-get install drweb-netcheck

If necessary, use help on the package manager of your OS.

Installation and Uninstallation of Dr.Web Mail Security Suite Components Installed from a Universal Package

If Dr.Web Mail Security Suite 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 Mail Security Suite. 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 Mail Security Suite installation files instead of starting the installation process;

--keep—do not delete Dr.Web Mail Security Suite installation files and the installation log after the installation;

--target <directory>—unpack Dr.Web Mail Security Suite 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:

$ ./<.run file name> --help

For custom installation of Dr.Web Mail Security Suite components, unpack the contents of the installation file. To do that, run the command:

$ ./<.run file name> --noexec --target <directory>

Custom Installation of Components

The .run installation file contains packages of all Dr.Web Mail Security Suite 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 Mail Security Suite. Names of all Dr.Web Mail Security Suite 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 service script. To do that, firstly unpack the contents of the installation package to any writeable directory.

To install packages, superuser (usually 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 another user.

To install a component package, go to the directory containing the unpacked installation file and run the command from the command line or from a terminal emulator:

# ./scripts/installpkg.sh <package_name>

For example:

# ./scripts/installpkg.sh drweb-netcheck

If it is necessary to install Dr.Web Mail Security Suite in full, start the installation script by running the command:

$ ./install.sh

Furthermore, you can install all Dr.Web Mail Security Suite packages (among other things, to install missing or accidentally removed components) by starting the installation of the root meta-package:

# ./scripts/installpkg.sh drweb-mail-servers

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-netcheck

If your OS uses DEB packages, or there is no package manager in your system (FreeBSD), for the custom uninstallation, use the zypper package manager supplied with Dr.Web Mail Security Suite. To do that, go to the directory /opt/drweb.com/bin for GNU/Linux or /usr/local/libexec/drweb.com/bin for FreeBSD and run the command:

# ./zypper remove <package_name>

For example:

# ./zypper remove drweb-netcheck

If you want to uninstall Dr.Web Mail Security Suite, start the uninstallation script by running the command:

# ./uninst.sh

To reinstall a component, you can uninstall it first and then install again by starting custom or full installation.