Installation - ESET GATEWAY SECURITY - FOR LINUX BSD AND SOLARIS Installation Manual

3. Installation

After purchasing ESET Gateway Security, you will receive your authorization data (username/password and license
key). This data is necessary for both identifying you as our customer and allowing you to download updates for ESET
Gateway Security. The username/password data is also required for downloading the initial installation package from
our web site. ESET Gateway Security is distributed as a binary file:
esets.i386.ext.bin
In the binary file shown above, 'ext' is a Linux, BSD and Solaris OS distribution dependent suffix, i.e., 'deb' for
Debian, 'rpm' for RedHat and SuSE, 'tgz' for other Linux OS distributions, 'fbs5.tgz' for FreeBSD 5.x, 'fbs6.tgz' for
FreeBSD 6.x, 'nbs4.tgz' for NetBSD 4.xx and 'sol10.pkg.gz' for Solaris 10.
Note that the Linux RSR binary file format is:
esets-rsr.i386.rpm.bin
To install or upgrade the product, use the following command:
sh ./esets.i386.ext.bin
For the Linux RSR variation of the product, use the command:
sh ./esets-rsr.i386.rpm.bin
to display the product's User License Acceptance Agreement. Once you have confirmed the Acceptance Agreement,
the installation package is placed into the current working directory and relevant information regarding the package's
installation, un-installation or upgrade is displayed onscreen.
Once the package is installed, you can verify that the main ESETS service is running by using the following
command:
Linux OS:
ps -C esets_daemon
BSD OS:
ps -ax | grep esets_daemon
Solaris:
ps -A | grep esets_daemon
After pressing ENTER, you should see the following (or similar) message:
PID TTY TIME CMD
2226 ? 00:00:00 esets_daemon
2229 ? 00:00:00 esets_daemon
At least two ESETS daemon processes are running in the background. The first PID represents the process and
threads manager of the system. The other represents the ESETS scanning process.
7