To stop the server:
Start method | Stop method |
From /etc/inittab (On AIX) | Enter stopsrc -s ibmproxy |
From /sbin/init.d (On HP-UX) | Enter /sbin/init.d/ibmproxy stop |
From /etc/rc.d/init.d (On Linux) | Enter /etc/rc.d/init.d/ibmproxy stop |
ibmproxy |
To stop all servers on this machine: Enter killall ibmproxy |
ibmproxy -nobg | Enter ctrl-c |
ibmproxy -r -other_config_file(On AIX) | Enter stopsrc -s ibmproxy -p process_id |
ibmproxy -r -other_config_file(On Linux) |
|
ibmproxy -unload
To stop the server at a root prompt, enter:
You can experience the following limitations when using the shutdown commands:
On AIX, HP-UX, and Linux systems, the commands to stop the Caching Proxy system sometimes shut down only the Caching Proxy process. The AIX command that results in this behavior is the stopsrc -s ibmproxy command. The HP-UX and Linux command that results in this behavior is the ibmproxy -stop command.
The PACD process, which is used by the LDAP server, might be left running after shutting down the proxy server. The PACD process can be safely shut down by using the kill command as follows:
kill -15 PACD_process_ID
Issuing the ibmproxy -stop command on a Solaris system does not have the same effect as the command does on other operating systems. Because of a limitation in Solaris code, the Server Termination plug-in step is not executed when ibmproxy -stop is used on Solaris platforms.
This limitation has implications for the proxy server software as well as for customer-implemented plug-ins.
It is possible for the PACD process, which is used by the LDAP server, to continue running after the proxy server is shut down. The PACD process can be safely shut down by using the kill command as follows:
kill -15 PACD_process_ID