egosetsystemd
Configures automatic startup of EGO on a Linux® host. The egosetsystemd.sh script supports the systemd daemon process, which starts processes in parallel, and reduces the boot time and computational overhead. (IBM® Spectrum Symphony also provides the egosetrc.sh script, which supports the init daemon process, which starts as soon as your system starts and continues running until it is shut down.) Depending on your system, use either egosetsystemd.sh or egosetrc.sh.
Synopsis
egosetsystemd.shDescription
Configures a Linux host to allow automatic startup of EGO on the machine when a system reboot command is issued. Creates the file ego under the system startup directory.
This is an administrative command. You must be logged on as root to issue this command.
Note that applying Fix 602717 fixes this
conflict; you do not require the following workaround after applying Fix 602717: There is
a known conflict between the systemd and egosh ego shutdown or
egosh ego restart commands; as a workaround, add
RemainAfterExit=yes in the $EGO_SERVERDIR/ego.service
file before running egosetsystemd.sh. For
example:ExecStart=/opt/ibm/spectrumcomputing/4.0/linux-x86_64/etc/ego_daemons.sh start
ExecStop=/opt/ibm/spectrumcomputing/4.0/linux-x86_64/etc/ego_daemons.sh stop
RemainAfterExit=yes- Restart the machine so that EGO can start up automatically.
- Run systemctl start ego as root so that the cluster runs at the expected
target unit.Note: Other than to set the egosetsystemd.sh script to automatically start EGO, do not use systemctl to control ego.service. To start and stop services and components for IBM Spectrum Symphony, use product's command line or the cluster management console instead.
If you do not configure hosts to start automatically, EGO must be started manually.
Unit section, add
the shared file system mount service in the After parameter. For example, for NFS
automount services, add autofs.service as
follows:[Unit]Description=IBM Spectrum Computing family: EGO
After=network.target autofs.service