Novell GROUPWISE 7 - MESSAGE TRANSFERT AGENT, Manual, Page: 47 / 97

Monitoring the MTA 649
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
Š
“Displaying Live Remote Status” on page 653
Š
“Displaying MTA Admin Thread Status” on page 653
Š
“Recovering the Domain Database Automatically or Immediately” on page 654
Š
“Performing eDirectory User Synchronization” on page 655
Š
“Browsing the Current MTA Log File” on page 655
Š
“Viewing a Selected MTA Log File” on page 656
Š
“Cycling the MTA Log File” on page 656
Š
“Adjusting MTA Log Settings” on page 656
Š
“Editing the MTA Startup File” on page 656
Š
“Accessing Online Help for the MTA” on page 657
Stopping the MTA
You might need to stop and restart the MTA for the following reasons:
Š
Updating the agent software
Š
Troubleshooting message flow problems
Š
Backing up the domain database
Š
Rebuilding the domain database
To stop the MTA from the MTA server console:
1 Click File > Exit > Yes to stop the MTA.
2 Restart the MTA, as described in the following sections in the GroupWise 7 Installation Guide :
Š
“ Starting the NetWare GroupWise Agents ”
Š
“ Starting the Linux GroupWise Agents as Daemons ”
Š
“ Starting the Windows GroupWise Agents ”
Stopping the Linux MTA When It Is Running as a Daemon
To stop the Linux MTA when it is running in the background as a daemon and you started it using
the grpwise script:
1 Make sure you are logged in as
root
.
2 Change to the /etc/init.d directory.
3 Enter the following command:
./grpwise stop
NetWare: Use Exit (F7). If the MTA does not respond to Exit, you can use the unload
command to stop the MTA. However, this might not allow the MTA to shut down
gracefully. In addition, the unload command stops all MTAs running on the server.
Linux: If the Linux MTA does not respond to Exit, you can kill the MTA process, as
described below, but include the -9 option.
Windows: If the Windows MTA does not respond to Exit, you can close the MTA server
console to stop the MTA or use the Task Manager to terminate the MTA task.