[Help Me] Eset file security on Slackware

FireGarden · 04-24-2009, 08:43 AM

does anyone ever install eset file security for linux?
they have support for .rpm n .deb

but for other distribution they provide .tgz.bin
i've tried to install it on my slackware box by runing

Code:

#./esets.i386.fbs5.tgz.bin

then it ask for agreement, anthen i type y for yes to accept the agreement

and then it compiled to a eset.tgz
when i installpkg, it did run well but without slac.desc
but when i check on kpackage, i noticed thet all the files were red crossed (dunno what it means) and i can't run the esets_daemon

does anyboy have a clue?

tommcd · 04-25-2009, 01:29 AM

Did you read through this document provided by Eset:
http://www.google.com/url?sa=t&sourc...wLkbQt09FlJK6w
It gives a different command for installing it on p10 of that document.

FireGarden · 04-27-2009, 02:56 AM

Quote:

Originally Posted by tommcd

Did you read through this document provided by Eset:
http://www.google.com/url?sa=t&sourc...wLkbQt09FlJK6w
It gives a different command for installing it on p10 of that document.

yes, i did read the manual

Code:

    This product is distributed as a binary file:
              esets.i386.ext.bin
    where ‘ext’ is a Linux/BSD/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.xx, ‘fbs6.tgz’ for
FreeBSD 6.xx, ‘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
    In order to install or update the product, use statement:
              sh ./esets.i386.ext.bin
    resp. for Linux RSR variation of the product, use statement:
              sh ./esets-rsr.i386.rpm.bin
    As a result the product’s User License Acceptance Agreement is shown. 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 update is printed into terminal.
    Once the package is installed and the main ESETS service is running, in Linux OS you can
check its operation by using command:
              ps -C esets_daemon
    In case of BSD OS you can use a command:
              ps -ax | grep esets_daemon
    In case of Solaris you can use a command:
              ps -A | grep esets_daemon
    You will see the following (or similar) message on return:
              PID TTY                   TIME CMD
              2226 ?                00:00:00 esets_daemon
              2229 ?                00:00:00 esets_daemon
    where at least two ESETS daemon processes running in the background have to be present.
One of the processes is so-called process and threads manager of the system. The other serves
as ESETS scanning process.

i followed the steps given n nothing went wrong with the installation, except the fact that the deamon was not running after the installation. i tried to run it manually but it's useless

nass · 04-27-2009, 04:28 AM

forgive me for sounding naive but,
all the articles i have come across in the web state how it is redundant to be running an anti virus service in unix systems...

has there been a shift in the views on this matter?

elmo40 · 05-12-2009, 01:14 PM

@nass
what if i have a file server? anyone can access files. anyone can upload files. would you still not be in need of a virus scanner?
anyone being lin/win/mac/...
stopping a potential spread is always a good idea.