AIX Down Under

If you want to get a view of the process tree, you could try it using the ps command, but there's a better way: the proctree command. You can see all of its parent processes and its child processes. Here's how it looks.

 

This is an installation of IBM Systems Director Management Server version 6.3.

 

 # ./dirinstall.server -B /database --DB=1

+=============================================================================+
Start of product installation on myhost

+=============================================================================+

 

Variables will be used during the installation:

  PRE_INSTALL_CHECKS : 1
  PRE_INSTALL_WARN_ABORT : 0
  PortNumber : 8421
  SecurePortNumber : 8422
  AGENT_MANAGER_PORT : 20000
  MIGRATE_DATA : 1
  UPDATES_PATH : /database/inst.images/packages/updates
  -Managed DB2 is supported and its prerequisites are met.
  DB_INST_TYPE : 1
  DB_DATAPATH : /database
  DB_PWD : default.
  DB_SERVER : localhost
  DB_PORT : default
+=============================================================================+
/tmp free space not enough, less than 1536M, trying to increase it...done
/home free space not enough, less than 1024M, trying to increase it...done
+-----------------------------------------------------------------------------+
Attempting to install Managed DB2...done
Attempting to install sysmgt.cimserver.pegasus Director.install.msg ....done

Attempting to install sysmgt.cim.providers...

To see what commands are being run at this stage, you can first find the Process ID (PID) of the Director installation command, dirinstall.server

 

 

Now you have the PID (in this case 8847562), you can run proctree.

 

 # proctree 8847562
3342538    /usr/sbin/srcmstr
   4063378    /usr/sbin/sshd
      8519734    sshd: root@pts/1
         9764866    -ksh
            8847562    /usr/bin/ksh ./dirinstall.server -B /database --DB=1
               9633942    /usr/sbin/installp -acgNQqXY -d /database/inst.images/packages sysmgt.cim.provi
                  4522126    /bin/ksh /usr/lib/instl/instal /database/inst.images/packages/sysmgt.cim.provid
                     5963860    /usr/bin/ksh sysmgt.cim.providers.osbase.config
                        9896132    /bin/ksh /opt/freeware/cimom/pegasus/etc/orig/rebuild_repository -fm
                           9175250    cimmofl -aE -W -w -R/opt/freeware/cimom/pegasus/etc -I/opt/freeware/cimom/pegas
                  13107380

 

Going down the tree shows that the dirinstall.server command is calling installp, which is installing some filesets for use by Systems Director.

Heading up the tree to parent processes, you can see that the dirinstall.server command is being run from the Korn shell (-ksh). This, in turn, is run out of an ssh (secure shell) session. The ssh daemon (sshd) was invoked by the System Resource Controller srcmstr.

The proctree command is well worth remembering. It can give you a quick view of the processes going up and down the tree.