2.3 Stopping Daemons

Stop daemons from the Management Server and Managed Server. Normally, they are automatically stopped on system shutdown.

To stop daemons on a server, execute the following command on the server:

# /opt/swstorage/bin/stopacm

Note

Before executing the stopacm command, confirm that the SWSTGNODE environment variable is not defined.

When the Management Server or Managed Server is in cluster operation, stop the daemon(s) from the clustered system. For the stop procedure, refer to the relevant cluster software manual.

To Stop Daemon Separately

To stop the daemon separately on AdvancedCopy Manager transactions in a clustered system, follow the steps described below:

You must stop the daemon in each AdvancedCopy Manager transaction (including local transactions) using the following procedure for the respective transactions.

Execute the following commands depending on the communication daemon to be operated and check if it is activated. If it is not activated, step 2 and subsequent steps are not necessary to be performed.
1. When the communication daemon is in the global zone and operation uses Oracle Solaris Zones Support Function.
```
# ps -z globale -f | grep stgxfws
```
2. When the target communication daemon is other than "a" described above.
```
# ps -ef | grep stgxfws
```
Confirm the command execution. If the strings are displayed as below, the daemon(s) is activated.
```
/opt/FJSVswstf/bin/stgxfws logicalNodeName
```
For the environment variable SWSTGNODE, specify the name of the logical node that the transaction is to be performed on.
Stop the communication daemon.
For the stop command, refer to "9.4.1 Starting and Stopping Communication Daemon".
Point
Terminating the communication daemon, may take up to 10 seconds to complete successfully.