In this section
•Typical Component Kits for a Custom Installation
•Dr.Web for UNIX File Servers Component Installation and Uninstallation:
▫installed from the repository
▫installed from the universal package
If necessary, you can choose to install or uninstall only certain Dr.Web for UNIX File Servers components by installing or uninstalling the respective packages. Perform custom component installation or uninstallation 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 Dr.Web for UNIX File Servers with the limited functionality, instead of installation of the 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 Dr.Web for UNIX File Servers 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 |
Packages for Installation |
Will be Installed |
|---|---|---|
Minimum kit 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 |
Suite for file system monitoring of GNU/Linux |
•drweb-se, •drweb-spider |
•Dr.Web ConfigD, •Dr.Web Ctl, •Dr.Web File Checker, •Dr.Web Scanning Engine, •Dr.Web Updater, •SpIDer Guard, •Virus database |
Suite for monitoring of shared Samba directories |
•drweb-se, •drweb-smbspider |
•Dr.Web ConfigD, •Dr.Web Ctl, •Dr.Web File Checker, •Dr.Web Scanning Engine, •Dr.Web Updater, •SpIDer Guard for SMB, •Virus database |
Suite for monitoring of NSS volumes |
•drweb-nss, •drweb-se |
•Dr.Web ConfigD, •Dr.Web Ctl, •Dr.Web File Checker, •Dr.Web Scanning Engine, •Dr.Web Updater, •SpIDer Guard for NSS, •Virus database |
Suite for the emulation ClamAV (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 database |
Installation and Uninstallation of Dr.Web for UNIX File Servers Components Installed from Repository
If Dr.Web for UNIX File Servers 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 Dr.Web for UNIX File Servers installed on CentOS, use the command:
# yum remove drweb-clamd |
2.To additionally install Dr.Web ClamD (package drweb-clamd) to Dr.Web for UNIX File Servers installed on OS Ubuntu, use the command:
# apt-get install drweb-clamd |
If needed, use help on package manager used in your OS.
Installation and Uninstallation of Dr.Web for UNIX File Servers Components Installed from the Universal Package
If Dr.Web for UNIX File Servers 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 Dr.Web for UNIX File Servers was installed. If you did not save this file, download it from the Doctor Web website.
Unpacking the Installation File
When you launch the .run file, you can also specify the following command-line parameters:
--noexec—unpack Dr.Web for UNIX File Servers 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 Dr.Web for UNIX File Servers installation files and the installation log automatically after the installation completes.
--target <directory>—unpack Dr.Web for UNIX File Servers 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 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 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 File 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 release, and <platform> is a platform for which Dr.Web for UNIX File Servers is intended. Names of all the packages containing the components of Dr.Web for UNIX File 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 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 Dr.Web for UNIX File Servers installation, launch the automatic installation script. To do that, use the command:
$ ./install.sh |
Besides that, you can install all Dr.Web for UNIX File Servers packages (to install the missing or accidentally deleted components as well) by launching the installation of the root meta-package:
# ./scripts/installpkg.sh drweb-file-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 MSVS 3.0 OS), or if there is no package manager in your system (FreeBSD), for the custom uninstallation, you should use the package manager zypper, which is automatically installed within the Dr.Web for UNIX File Servers installation. To do that, go to the directory <opt_dir>/bin (for GNU/Linux—/opt/drweb.com/bin) and execute the command:
# ./zypper remove <package_name> |
For example:
# ./zypper remove drweb-clamd |
If you need to uninstall Dr.Web for UNIX File Servers, launch the automatic removal script. To do this, enter the 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.