Custom Component Installation and Uninstallation

 Top  Previous  Next

If necessary, you can choose to install or uninstall only certain product components by installing or uninstalling the respective packages. Custom component installation or uninstallation should be performed the same way the product was installed.

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

Typical Component Kits for a Custom Installation

If it is required to install the product with the limited functionality, instead of installation of the product’s root meta-package from the repository or from the universal package, you can install only component packages that provide the required functionality. The packages required to resolve dependencies will be automatically installed. The table below displays component sets designed to resolve typical product tasks. In the column Package for Installation, there is a list of packages required for installation to obtain the specified component suite.

Custom Component Kit

Package for Installation

Will be Installed

Minimum kit for console scanning

drweb-filecheck

•Dr.Web Ctl

•Dr.Web ConfigD

•Dr.Web Scanning Engine

•Dr.Web File Checker

•Dr.Web Updater

•Virus database

Suite for the emulation ClamAV (clamd)

drweb-clamd

•Dr.Web Ctl

•Dr.Web ConfigD

•Dr.Web Scanning Engine

•Dr.Web File Checker

•Dr.Web Network Checker

•Dr.Web Updater

•Dr.Web ClamD

•Virus database

Suite for scanning email as a filter that could be connected to MTA

Note: If the anti-virus scanning of email messages is not required, packages drweb-netcheck and drweb-se are not required for installation. The package drweb-se could be skipped for installation if the anti-virus scanning is performed on another server, which receives data for scanning via Dr.Web Network Checker. The package drweb-dws could be skipped for installation if there is no requirement for the URL to be included in the categories of unwanted web resources. Packages drweb-antispam and drweb-vaderetro could be skipped for installation if email message scanning for spam is not required.

Mark *) labels components that will not be installed if the package drweb-se is not installed. Mark **) labels components that will not be installed if the package drweb-dws is not installed. The component Dr.Web Updater (marked with ***) will be installed only if virus databases or database of web resource categories are installed. Mark ****) labels components that will not be installed if packages that check for spam are not installed. The Dr.Web Updater component (labeled with ***) will be installed only if virus databases, web resource category database and the Vaderetro spam filter are installed.

drweb-maild
drweb-dws ***
drweb-antispam **
drweb-vaderetro **
drweb-netcheck *
drweb-se *

•Dr.Web Ctl

•Dr.Web ConfigD

•Dr.Web MailD

•Dr.Web ASE ****)

•VadeRetro spam filter ****)

•Dr.Web Network Checker

•Dr.Web Scanning Engine *)

•Dr.Web Updater ***)

•Virus database *)

•Database of web resource categories **)

Suite for scanning email in the transparent proxy mode for the protocols SMTP, POP3, IMAP

Note: If the anti-virus scanning of email messages is not required, packages drweb-netcheck and drweb-se are not required for installation. The package drweb-se could be skipped for installation if the anti-virus scanning is performed on another server, which receives data for scanning via Dr.Web Network Checker. The package drweb-dws could be skipped for installation if there is no requirement for the URL to be included in the categories of unwanted web resources. Packages drweb-antispam and drweb-vaderetro could be skipped for installation if email message scanning for spam is not required.

Mark *) labels components that will not be installed if the package drweb-se is not installed. Mark **) labels components that will not be installed if the package drweb-dws is not installed. The component Dr.Web Updater (marked with ***) will be installed only if virus databases or database of web resource categories are installed. Mark ****) labels components that will not be installed if packages that check for spam are not installed. The Dr.Web Updater component (labeled with ***) will be installed only if virus databases, web resource category database and the Vaderetro spam filter are installed.

drweb-gated
drweb-firewall
drweb-maild
drweb-dws ***
drweb-antispam **
drweb-vaderetro **
drweb-netcheck *
drweb-se *

•Dr.Web Ctl

•Dr.Web ConfigD

•SpIDer Gate

•Dr.Web Firewall for Linux

•Dr.Web MailD

•Dr.Web ASE ****)

•VadeRetro spam filter ****)

•Dr.Web Network Checker

•Dr.Web Scanning Engine *)

•Dr.Web Updater ***)

•Virus database *)

•Database of web resource categories **)

1. Installation and Uninstallation of Product Components Installed from Repository

If your product is installed from repository, for custom component installation or uninstallation use the respective command of the package manager, used in your OS. For example:

1.To uninstall Dr.Web ClamD (package drweb-clamd) from the product installed on OS CentOS, use the command:

# yum remove drweb-clamd

2.To additionally install Dr.Web ClamD (package drweb-clamd) to the product installed on OS Ubuntu Linux, use the command:

# apt-get install drweb-clamd

If necessary, use a help file of the package manager used in your OS.

The Dr.Web for UNIX Mail Servers anti-virus engine uses a 32-bit architecture x86; in 64-bit systems Debian, Mint, Ubuntu (for platforms x86-64, x64, amd64), a permission could be required for installation of packages for the platform x86. It could be obtained via the following command:

# dpkg --add-architecture i386

2. Installation and Uninstallation of Product Components Installed from the Universal Package

If the product is installed from the 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), from which the product was installed. In case you did not save this file, download it from the Doctor Web’s official website.

Unpacking the Installation File

When you launch the .run file, you can also specify the following command-line parameters:

--noexec—unpack the product’s installation files instead of starting the installation process. The files will be placed to the directory that is specified in the TMPDIR environment variable (usually, /tmp).

--keep—do not delete the product installation files and the installation log automatically after the installation completes.

--target <directory>—unpack the product’s installation files to the specified <directory>.

For a full list of command-line parameters that can be specified for the launching of the .run file, enter the following command:

$ ./<file_name>.run --help

For a custom installation, you need to use the unpacked installation files. If there is no directory containing these files, you should first unpack them. To do that, enter the following command:

$ ./<file_name>.run --noexec --target <directory>

After the command is executed, a nested directory named <file_name> will appear in the directory <directory>.

Custom Installation of the Components

Installation RUN file contains packages of all components of Dr.Web for UNIX Mail Servers (in the RPM format) and supporting files. Package files of each component have the following structure:

<component_name>_<version>~linux_<platform>.rpm

where <version> is a string that contains the version and time of the product’s release, and <platfrom> is a platform for which the product is intended. Names of all the packages containing the components of Dr.Web for UNIX Mail Servers start with the "drweb" prefix.

Package manager is enabled for the installation of packages to the installation kit. For the custom installation, you should use a service script installpkg.sh. To do that, first, you need to unpack the contents of the installation package to a directory.

To install packages, superuser permissions are required (i.e. privileges of the root user). To elevate your privileges, use the su command for changing the current user or the sudo command to execute the specified command with the privileges of another user.

To start installation or reinstallation of a component package, go to the directory which contains the unpacked installation kit, and execute the following command via the console (or via a console emulator—terminal for the graphical mode):

# ./scripts/installpkg.sh <package_name>

For example:

# ./scripts/installpkg.sh drweb-clamd

If it is necessary to start the full product installation, launch the automatic installation script. To do that, use the following command:

$ ./install.sh

Besides that, you can install all product packages (to install the missing or accidentally deleted components as well) by launching the installation of the root meta-package of the product:

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

Custom Uninstallation of the Components

For the custom uninstallation of a component, use the appropriate uninstallation command of the package manager of your OS if your OS uses the RPM format of packages:

•In Red Hat Enterprise Linux and CentOS, use the command yum remove <package_name>

•In Fedora, use the command yum remove <package_name> or dnf remove <package_name>

•In SUSE Linux, use the command zypper remove <package_name>

•In Mageia, OpenMandriva Lx, use the command urpme <package_name>

•In Alt Linux and PCLinuxOS, use the command apt-get remove <package_name>.

For example (for Red Hat Enterprise Linux):

# yum remove drweb-clamd

If your OS uses DEB packages (also if you use MSVS 3.0 OS), or if there is no package manager in your system (FreeBSD, Solaris), for the custom uninstallation, you should use the package manager zypper, which is automatically installed within the product installation. To do that, go to the directory <opt_dir>/bin (for GNU/Linux—/opt/drweb.com/bin) and execute the following command:

# ./zypper remove <package_name>

For example:

# ./zypper remove drweb-clamd

If it is necessary to start the full product uninstalling, launch the automatic uninstallation script. To do that, use the following command:

# ./uninst.sh

To reinstall a component, you can uninstall it first and then install by launching the custom or full installation from the installation kit.