Table of Contents
Advertisement
196
C
10: O
HAPTER
PERATIONS
must take place through the EMS CLI client. The EMS server will,
however, continue to log all output to the daily
ServerConsoleLog-yyyymmdd.log located in the <EMS_root>/log
directory. On UNIX platforms, you may tail this file to monitor the server
startup progress.
When launched as a background process or daemon, the EMS server
will still issue its normal startup messages to the console.
3Com recommends that you only run the EMS server as a daemon when
there is no expected interaction required with the EMS server command
prompt. For example, make sure that you have already entered a valid
license so that you do not get prompted for it every time you attempt to
start the server in daemon mode.
Starting the Server as a UNIX Background Process
Run the EMS server as a UNIX background process using the optional
-daemon parameter in one of two ways:
Run the EMS server as a background process, using the following
■
command:
./runServer -daemon &
This will start the EMS server and force the EMS process into the
background, returning control of the terminal back to the user.
However, shutting down the terminal window will stop the EMS
server.
Run the EMS server in a mode where it is detached from the terminal
■
that it was launched from. Once the EMS server starts (for example,
from a remote Telnet window), it is possible to shut down the terminal
window (and the Telnet session) and still make sure that the EMS
server is running. The standard UNIX nohup command is used to make
this possible.
To launch the EMS server in this mode, enter the following command
from the EMS installation directory:
nohup ./runServer -daemon &
For both options, the only way to send commands to the EMS server (for
example, to stop the server), is to use the EMS CLI client.
It is possible to incorporate these startup modes in your system
initialization sequence (for example, as part of your bootup rc or init
Advertisement
Table of Contents
