Controlling Infrastructure Engines
The Appliance Stack product runs numerous infrastructure "Engines" Each has a unique name (although it isn't required unless they share services).    The old datacenter runs pods servers using a configuration named "podsys".    The Appliance Stack has 3 "Engines" "mcu" on the MCU, "sdm" on the SDM, and "bcm" on the BCM.

Infrastructure Control Tool (infCtl): InfCtl makes heavy use of the ctl layer which is dependent on the sys layer.   

To start an engine, use the command: sysgo configName.    The command prompt will immediately return (if sysgo is not configured to run in the foreground).

To start or restart a process that has been stopped, bring up the infrastructure control tool (infCtl config), enter 'p' for the process control sub-menu, then 's' for start a process, the system will display an indexed list of processes.    Enter the index number of the process you wish to start.

To stop an engine use infCtl configName, then, at the first menu, enter 'k' to Kill the system.    Sysgo will shutdown all sub-processes then exit. You may also do a "kill sysgoPid", which will shutdown all sub-processes and exit.

If sysgo had previously exited some sub-processes are still up, re-issue sysgo configName, and sysgo will re-acquire control of the running sub-processes and start new ones for any that have died.   

A second tool is available to talk to remote systems called infRmt.    It requires a configuration file which only contains TCP definitions for each remote system's Orb.    This tool uses event forawarding done by the ctl layer and normally uses the Orb's external listening port to communicate.