Novell GROUPWISE 8 - ADMINISTRATION Administration Manual page 535

Stopping the Linux POA When It Is Running As a Daemon
To stop the Linux POA when it is running in the background as a daemon and you started it using
the script:
grpwise
1 Make sure you are logged in as
2 Change to the
/etc/init.d
3 Enter the following command:
./grpwise stop
4 Use the following command to verify that the POA has stopped.
./grpwise status
To stop the Linux POA when it is running in the background as a daemon and you started it
manually (not using the grpwise script):
1 Determine the process IDs (PIDs) of the POA:
ps -eaf | grep gwpoa
The PIDs for all gwpoa processes are listed.
You can also obtain this information from the
2 Kill the first POA process listed:
Syntax:
kill PID
Example:
kill 1483
It might take a few seconds for all POA processes to terminate.
3 Use the ps command to verify that the POA has stopped.
ps -eaf | grep gwpoa
Suspending/Resuming the POA Admin Thread
You can cause the POA to stop accessing the post office database (
POA completely. For example, you could suspend the POA admin thread while backing up the post
office database.
To suspend the POA admin thread:
1 At the POA server console, click Configuration > Admin Status.
2 Click Suspend.
NetWare Note: Use Options (F10) > Admin Status > Suspend.
The POA admin thread no longer accesses the post office database until you resume processing.
To resume the POA admin thread:
1 At the POA server console, click Configuration > Admin Status.
2 Click Resume.
NetWare Note: Use Options (F10) > Admin Status > Resume.
.
root
directory.
Environment page of the POA Web console.
) without stopping the
wphost.db
Monitoring the POA 535