Checking Whether Logservice Is Running

1. Telnet to the system or open the terminal.

2. Check system processes.

ps -ef | grep logservice

3. Observe the contents displayed on the screen. If the result includes the logservice path name as shown

in the following example, it indicates logservice is running. If the result is NULL or just includes grep

logservice, it indicates logservice is not running.

[root@ommleft ~]# ps -ef | grep logservice

root 23913 1 0 Feb10 pts/1 00:03:54 /home/zte/logservice/bin/../bin/SysCtrlProc

root 23928 23913 0 Feb10 pts/1 00:38:36 /home/zte/logservice/bin/../bin/CommProc BOARD_MASTER

BOARD_LEFT

root 23929 23913 0 Feb10 pts/1 00:00:24 /home/zte/logservice/bin/MoAdaptProc BOARD_MASTER

BOARD_LEFT

root 23971 23913 2 Feb10 pts/1 01:27:24 /home/zte/logservice/bin/../bin/CommonLogProc

BOARD_MASTER BOARD_LEFT

root 23997 23913 0 Feb10 pts/1 00:04:51 /home/zte/logservice/bin/../bin/GLogProc BOARD_MASTER

BOARD_LEFT

root 24023 23913 0 Feb10 pts/1 00:00:01 /home/zte/logservice/bin/../bin/TDLogProc BOARD_MASTER

BOARD_LEFT

root 24049 23913 0 Feb10 pts/1 00:00:01 /home/zte/logservice/bin/../bin/WLogProc BOARD_MASTER

BOARD_LEFT

root 27235 27210 0 08:57 pts/7 00:00:00 grep logservice

Start Logservice with command. #cd /home/zte/logservice/bin/

#./startsys

Execute the above commands on the left board and the right board respectively to start the master/slave

processes on the boards respectively. The OMM on which OmmHost runs first will act as the master

board, and the OMM on which OmmHost runs later will act as the slave board.

Stop Logservice with command #cd /home/zte/logservice/bin/

#./stopsys

Execute the above commands on the left board and the right board respectively to start the

master/slave processes on the boards respectively. The OMM on which OmmHost runs first will act

as the master board, and the OMM on which OmmHost runs later will act as the slave board.