The deployall tool installs the required startup scripts into the correct location so that all required services can be automatically started and stopped during the startup and shutdown of your server.
To use, the tool should be executed with superuser privileges, either directly using sudo, or by logging in as the superuser and running the command directly.
The script will automatically detect the initialization system in use
(systemd or initd)
and prefer systemd when both are available.
shell> sudo deployall
In order for the configuration to persist during future updates, and/or
to execute the deployall script at install time, you should add the
install=true tpm option to your configuration
The startup scripts are added to the correct run levels to enable operation during standard startup and shutdown levels.
For systemd configurations only:
For continuity of service reasons, the deployall script will NOT restart individual components if they had already been previously started by other methods. It will only install systemd scripts. This implies that, right after a call to deployall and before host/component restart, the system will stay in a mixed mode where systemd scripts are in place but components that were started without systemd, won’t be controllable by it.
In order to align the configuration, you will need to run
shell>shell>componentstop sysdsudo systemctl start tcomponent
For example:
shell>connector stop sysdshell>sudo systemctl start tconnector
See Section 2.5, “Configuring Startup on Boot”.
To remove the scripts from the system, use undeployall.