Topics: IBM Content Manager

Starting and stopping Content Manager On Demand

Start:

# Start Content Manager on Demand
echo Starting CMOD...
su - archive -c "/usr/lpp/ars/bin/arssockd ARCHIVE"
echo CMOD started.
Stop:
# First kindly request CMOD to stop.
echo Stopping CMOD...
su - archive -c "/usr/lpp/ars/bin/arssockd stop ARCHIVE"
# Wait 10 seconds for CMOD to stop.
sleep 10
# If it is still active - then kill the process
PROCESS=$(ps -ef | grep "arssockd: (accepting)" | grep -v grep | awk '{ print $2 }' )
if [ -n "$PROCESS" ] ; then
   echo CMOD did not stop correctly.
   kill $PROCESS
   echo CMOD process killed.
else
   echo CMOD stopped.
fi
It's actually allowed to kill the process, if a normal stop request fails. CMOD doesn't notify you whether the process stopped or started successfully or not, so you have to check it. It occasionally occurs that CMOD doesn't want to stop. If that happens, just kill the accepting process.



If you found this useful, here's more on the same topic(s) in our blog:


UNIX Health Check delivers software to scan Linux and AIX systems for potential issues. Run our software on your system, and receive a report in just a few minutes. UNIX Health Check is an automated check list. It will report on perfomance, capacity, stability and security issues. It will alert on configurations that can be improved per best practices, or items that should be improved per audit guidelines. A report will be generated in the format you wish, and the report includes the issues discovered and information on how to solve the issues as well.

Interested in learning more?