Unpacking installation file
If you choose to install only certain product components, unpack the installation file <file_name>.run without running an installation program. For that, specify the --noexec command-line parameter as follows:
$ ./<file_name>.run --noexec
After the command is executed, a nested directory <file_name> appears in the current directory.
You can also specify the following command-line parameters when launching the run-file:
-keep — instructs to unpack product installation files of the <file_name> directory to the current one (and not to /tmp), which prevents automatic deletion of files after the installation completes.)
--target <path_to_directory> — instructs to unpack product installation files of the <file_name> directory to the specified one. Note that the unpacked files will be automatically detected after the installation completes unless you specify one of the following parameters: --noexec or --keep.
For a full list of command-line parameters that can be specified for an installation file, type the following command:
$ ./<file_name>.run --help
Custom Installation
Installation directory contains packages of all Dr.Web for UNIX File Servers components and supporting files. The package of every component <component_name> contains two files: <component_name>.install and <component_name>.remove. These files are command scripts. The first script is used to install the component, the second script—to remove the component. Names of all packages containing components of Dr.Web for UNIX File Servers are started with the drweb. prefix.
In general, the archive contains the following packages:
Package |
Content |
|---|---|
drweb-bases |
Files of anti-virus engine Dr.Web Virus-Finding Engine and Dr.Web virus databases |
drweb-boost |
Boost framework libraries |
drweb-clamd |
Files of Dr.Web ClamD component |
drweb-common |
Main configuration file drweb.ini, libraries, documentation, and directory structure During the installation, drweb user and drweb group are created. |
drweb-configd |
Files of Dr.Web ConfigD и Dr.Web Ctl |
drweb-epm10.1.0-libs |
Supporting libraries for installation program |
drweb-epm10.1.0-uninst |
Supporting libraries for uninstallation program |
drweb-esagent |
Files of Dr.Web ES Agent component |
drweb-filecheck |
Files of Dr.Web File Checker component |
drweb-file-servers-doc |
PDF documentation for the solution |
drweb-file-servers |
Root meta-package of the solution |
drweb-httpd |
Files of Dr.Web HTTPD component and management web interface |
drweb-icu |
Unicode and internationalization supporting libraries |
drweb-libs * |
Common libraries of the solution |
drweb-netcheck |
Files of Dr.Web Network Checker component |
drweb-nss |
Files of SpIDer Guard for NSS component |
drweb-openssl |
OpenSSL framework libraries |
drweb-protobuf |
Protobuf framework libraries |
drweb-se |
Files of Dr.Web Scanning Engine component |
drweb-smbspider-daemon |
Files of SpIDer Guard for SMB component (SMB monitoring daemon) |
drweb-smbspider |
Files of SpIDer Guard for SMB component |
drweb-smbspider-modules |
Files of SpIDer Guard for SMB component (VFS SMB modules) |
drweb-smbspider-modules-src |
Files of SpIDer Guard for SMB component (VFS SMB module source codes) |
drweb-snmpd |
Files of Dr.Web SNMPD component |
drweb-spider |
Files of SpIDer Guard component |
drweb-spider-kmod |
Files of SpIDer Guard component (loadable kernel module for LKM mode) |
drweb-update |
Files of Dr.Web Updater component |
drweb-wt |
Wt framework libraries (used by management web interface) |
*) Versions for 64-bit systems include two packages: drweb-libs and drweb-libs32 that contain libraries for 64-bit and 32-bit components accordingly.
To start installation of a component, run the corresponding installation file from the console (or via a console emulator — terminal for the graphics mode).
|
Installation scripts can be run only by a user with administrative privileges (root superuser). To elevate privileges, use the su command (change the current user) or the sudo command (execute the specified command with other user privileges). |
When installing any component, all dependencies are automatically resolved, that is, if another component is required for installation, its presence in the system is checked and the required component is automatically installed if it is missing.
If it is necessary to run a program for installing the whole suite, run the automatic installation script from the unpacked directory by typing the following command:
$ ./install.sh