Installation from Distribution Package for UNIX Systems

Dr.Web for UNIX File Servers solution is distributed as a self-extracting package
drweb-file-servers_[version number]~[OS name].run.

The following components are included in this distribution:

drweb-common: contains the main configuration file - drweb32.ini, libraries, documentation and directory structure. During installation of this component, drweb user and drweb group are created;

drweb-bases: contains Anti-virus search Engine (Dr.Web Engine) and virus databases. It requires drweb-common package to be installed;

drweb-libs: contains common libraries for all the components of the suite;

drweb-epm6.0.2-libs: contains libraries for graphical installer and uninstaller. It requires drweb-libs package to be previously installed;

drweb-epm6.0.2-uninst: contains files of graphical uninstaller. It requires drweb-libs package to be previously installed;

drweb-boost147: containes common libraries for Dr.Web Agent and Dr.Web Monitor. It requires drweb-libs package to be previously installed;

drweb-updater: contains update utility - Dr.Web Updater for Dr.Web Engine and virus databases. It requires drweb-common and drweb-libs packages to be installed;

drweb-agent: contains Dr.Web Agent executable files and its documentation. It requires drweb-common and drweb-boost147 packages to be installed;

drweb-agent-es: contains files required for communication between Dr.Web Agent and Dr.Web ESS server version 6 in central protection mode. It requires drweb-agent, drweb-updater and drweb-scanner packages to be installed;

drweb-agent10: contains executable files and documentation for the updated Dr.Web Agent (designed for operation with Dr.Web ESS server version 10).

drweb-agent10-es: contains files required for communication between the updated Dr.Web Agent and Dr.Web ESS server version 10 in central protection mode.

drweb-daemon: contains Dr.Web Daemon executable files and its documentation. It requires drweb-bases and drweb-libs packages to be previously installed;

drweb-scanner: contains Dr.Web Scanner executable files and its documentation. It requires drweb-bases and drweb-libs packages to be installed;

drweb-monitor: contains Dr.Web Monitor executable files and its documentation. It requires drweb-agent, drweb-common and drweb-boost147 packages to be installed;

drweb-samba-web: contains web interface - Dr.Web Console for UNIX File Servers;

drweb-file-servers-doc: contains Dr.Web for UNIX File Servers documentation;

drweb-smbspider: contains compiled libraries for different versions of Samba servers. It requires drweb-libs;

drweb-smbspider-src: contains source codes used to build necessary libraries for specific version of Samba.

In distributions for 64-bit systems, two additional packages are included: drweb-libs and drweb-libs32, which contain libraries for 64 and 34-bit systems correspondingly.

To install all Dr.Web for UNIX File Servers components automatically, use either console (CLI) or the default file manager of your GUI-based shell. In the first case, allow the execution of the corresponding self-extracting package with the following command:

chmod +x drweb-file-servers_[version number]~[OS name].run

and then run it:

# ./drweb-file-servers_[version number]~[OS name].run

As a result, drweb-file-servers_[version number]~[OS name] directory is created, and the GUI installer starts. If it starts without root privileges, the GUI installer tries to gain required privileges.

If the GUI installer fails to start, then interactive console installer starts automatically.

If you need only to extract the content of the package without starting the GUI installer, use --noexec command line parameter:

# ./drweb-file-servers_[version number]~[OS name].run --noexec

After you extract the content, you can start the GUI installer and continue setup with the following command:

# drweb-file-servers_[version number]~[OS name]/install.sh

To install with the use of the console installer, use the following command:

# drweb-file-servers_[version number]~[OS name]/setup.sh

Installation, regardless of the used method, includes the following steps:

Original configuration files are recorded to the %etc_dir/software/conf/ directory with the following names: [configuration_file_name].N.

Operational copies of configuration files are installed to the corresponding directories.

Other files are installed. If a file with the same name already exists in the directory (e.g. after inaccurate removal of previous package versions), it is overwritten with the new file, and a copy of the old one is saved as [file_name].O. If a file with the [file_name].O name already exists in this directory, it is replaced with the new file.

If you select the Run interactive postinstall script check box in the corresponding window of the GUI installer, then after installation of the components completes, the post-install script is initialized for Dr.Web for UNIX File Servers basic adjustment.

Script update-links.sh is initialized to check the version of Samba installed in the system. The script creates a symbolic link in the /usr/lib/samba/vfs/ directory to the library required for the Samba version. If different Samba versions are installed to the same directory, a symbolic link is created to only one of the versions. If different Samba versions are installed to different directories, a symbolic link to each of the libraries is created. At that, the following text is logged for each installed Samba:

Example for Linux:

Update links for /usr/sbin/smbd
create symlink /opt/drweb/lib/libsmb_spider.so.3.X.X --> /usr/lib/samba/vfs/smb_spider.so
Please, update your config /etc/samba/smb.conf

 

Внимание!

Please note that if the used Linux distribution features SELinux, installation can be interrupted by the security subsystem. If such situation occurs, set SELinux to (Permissive) mode. To do this, enter the following command:

# setenforce 0

and restart the installer.

After the installation completes, configure SELinux security policies to enable correct operation of anti-virus components.

You can remove the drweb-file-servers_[version number]~[OS name] directory and .run file after successful completion of installation.