ESET North America Server NOD32 Benutzerhandbuch
Chapter 4. NOD32LMS package installation
that should return the following or simillar message
PID TTY
TIME CMD
2226 ?
00:00:00 nod32d
If this is not the case, then something is wrong and you should report this as a bug to the NOD32
support service.
As you will soon realize, there are also other daemons within a NOD32LMS package that are re-
quired to run in some system configurations. For instance the daemon nod32smtp or nod32smfi.
However, since the functionality of these daemons is not required in all cases, the installation
script does not provide the automatic start-up of them at system boot. If necessary one has to do
it by hand. Here is the description of how to do this.
In order to start, for instance, nod32smtp daemon under Red Hat or Mandrake, one has to write
the following command
support service.
As you will soon realize, there are also other daemons within a NOD32LMS package that are re-
quired to run in some system configurations. For instance the daemon nod32smtp or nod32smfi.
However, since the functionality of these daemons is not required in all cases, the installation
script does not provide the automatic start-up of them at system boot. If necessary one has to do
it by hand. Here is the description of how to do this.
In order to start, for instance, nod32smtp daemon under Red Hat or Mandrake, one has to write
the following command
/sbin/service nod32smtp start
Under SuSE the appropriate command would be
/sbin/startproc /usr/bin/nod32smtp
Finally, for the Debian the equivalent command is
/sbin/start-stop-daemon --start --exec /usr/sbin/nod32smtp
Similarly, for stopping the appropriate service, one would write under RedHat or Mandrake the
following command
following command
/sbin/service nod32smtp stop
Under SuSE the appropriate command would be
/sbin/killproc /usr/bin/nod32smtp
and for Debian the equivalent command is
/sbin/start-stop-daemon --stop --name nod32smtp
Above are the useful commands always used when reconfiguring the system (in this case the
NOD32LMS system always has to be restarted).
Now we will describe how to provide the automatic start of the daemon at system boot. In order
to do so, one has to write under Red Hat or Mandrake system the following commands
NOD32LMS system always has to be restarted).
Now we will describe how to provide the automatic start of the daemon at system boot. In order
to do so, one has to write under Red Hat or Mandrake system the following commands
10