Disabling the automatic startup of openFT

This section only applies to openFT versions <= V12.1C, since from version V12.1C systemd is used.

This section does not apply to Solaris, because openFT V12.1 does not support automatic start-up of openFT on Solaris without SMF. A different mechanism is used for Solaris with SMF, see section “Solaris SMF”.

During installation, the startup file is installed, e.g. /sbin/rc2.d/S910openFT on HP-UX, /etc/rc3.d/S50openFT on RedHat Linux and /etc/rc.ft on AIX. This script calls the file /var/openFT/std/etcinit/openFTinst when the system starts, which then automatically starts openFT.

If openFT instances were created using the ftcrei command, then this script also calls the startup and shutdown file for this instance (see also section “openFT instances and cluster operation”).

These files then start openFT on each openFT instance.

If you do not want openFT to be started automatically, you will need to
comment out the corresponding command line in the file /var/openFT/std/etcinit/openFTinst or in the startup and shutdown file for the instances.

Automatic termination of openFT

During installation, the shutdown file is installed (e.g. /sbin/rc1.d/K200openFT on HP-UX or /etc/rc0.d/K50openFT on RedHat Linux or /etc/rc.ft on AIX). This script calls the file /var/openFT/std/etcinit/openFTinst when the system shuts down, which then automatically terminates openFT.

If openFT instances were created using the ftcrei command, then this script also calls the startup and shutdown files for these instances (see also section “openFT instances and cluster operation”).

These files then terminate the corresponding openFT instance.