In this section
•Typical Component Sets for Custom Installation
•Component Installation and Uninstallation of Dr.Web for UNIX File Servers:
▫installed from a 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 installation or uninstallation the same way Dr.Web for UNIX File Servers 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 for UNIX File Servers 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 for UNIX File Servers 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 GNU/Linux file system monitoring |
•drweb-se, •drweb-spider |
•Dr.Web ConfigD, •Dr.Web Ctl, •Dr.Web File Checker, •Dr.Web Scanning Engine, •Dr.Web Updater, •SpIDer Guard, •Virus databases |
Set for monitoring 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 databases |
Set for monitoring 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 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 |
Installation and Uninstallation of Dr.Web for UNIX File Servers Components Installed from a Repository
If Dr.Web for UNIX File Servers is installed from a repository, to install or uninstall a component, use the 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 for UNIX File Servers 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 for UNIX File Servers 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 for UNIX File Servers Components Installed from a Universal Package
If Dr.Web for UNIX File Servers 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 for UNIX File Servers. 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 for UNIX File Servers 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 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 used with the installation file, run the command:
$ ./<file_name>.run --help |
Prior to custom installation of Dr.Web for UNIX File Servers components, unpack the contents of the installation file. To do that, run the command:
$ ./<file_name>.run --noexec --target <directory> |
As the result, a nested directory named <file_name> with the contents of the installation file will be created in the <directory> directory.
Custom Installation of Components
The .run installation file contains packages of all Dr.Web for UNIX File Servers 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 the package release, and <platform> is a platform to run Dr.Web for UNIX File Servers. Names of all Dr.Web for UNIX File Servers component packages start with the drweb prefix.
The installation kit is bundled with a package manager. For custom installation, use the installpkg.sh service script. Prior to that, unpack the contents of the installation file.
|
To install packages, superuser (root) permissions are required. To elevate your privileges, use the su command for changing the current user or the sudo command to run the specified command as another user. |
To install a component package, go to the directory with the contents of the unpacked installation file, and run the command via the console (or via a console emulator—a terminal for the graphical mode):
# ./scripts/installpkg.sh <package_name> |
For example:
# ./scripts/installpkg.sh drweb-netcheck |
If it is necessary to install Dr.Web for UNIX File Servers in full, start the automatic installation script by running the command:
$ ./install.sh |
Besides that, you can install all Dr.Web for UNIX File Servers packages (among other things, to install necessary or accidentally removed components) by starting the installation of the root meta-package:
# ./scripts/installpkg.sh drweb-file-servers |
Custom Uninstallation of Components
If your OS uses the RPM format of packages, to uninstall a single component, use the appropriate 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 Linux or PCLinuxOS, 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 (including MSVS 3.0), or there is no package manager in your system (FreeBSD), for the custom uninstallation, you should use the zypper package manager, which is automatically installed with Dr.Web for UNIX File Servers. To do that, go to the <opt_dir>/bin directory (/opt/drweb.com/bin for GNU/Linux) and run the command:
# ./zypper remove <package_name> |
For example:
# ./zypper remove drweb-netcheck |
If you want to uninstall Dr.Web for UNIX File Servers, start the automatic removal 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.