Run the daemon.sh Command Line Tool
The daemon.sh command line tool is located in the Software AG_directory/common/bin directory. Log on to your system as the root user and call it from any current working directory.
The rc-script names and locations are listed in Product Daemons and rc-scripts.
Important: The listed rc-scripts might offer options to install or uninstall, but
these are daemon registration methods implemented by Tanuki Software, Ltd. and are not
supported by IBM. Use only the start or stop options with the rc-scripts, and use only daemon.sh to register
or un-register daemons.
The table below lists the most commonly used command line options for the daemon.sh command line tool; they are the same for every supported UNIX platform.
| Action | Command with Option |
|---|---|
| Register daemon with default system file name | daemon.sh -f absolute_path_to_rc-script
|
| Register daemon and specify instance name | daemon.sh -f absolute_path_to_rc-script -n
instance
|
List all registered daemons that have prefix sag |
daemon.sh -L |
| Unregister daemon | daemon.sh -r -f absolute_path_to_rc-script
|
| Remove daemon registrations for which rc-script no longer exists (clean up) | daemon.sh -C |
| Print information about implementation and other command line options | daemon.sh -h |
| For RHEL 7+ and SLES12+ (systemd), Register daemon to start before a dependent daemon | daemon.sh -f absolute_path_to_rc_script
-B dependent_service_file_basename |
| For RHEL 7+ and SLES12+ (systemd), Register daemon to start after a dependent daemon | daemon.sh -f absolute_path_to_rc_script
-A dependent_service_file_basename |
| For RHEL 7+ and SLES12+ (systemd), Load non-default login shell environment | daemon.sh -f absolute_path_to_rc_script
-E comma_separated_list_of_environment_files |
| For RHEL 7+ and SLES 12+ (systemd),Ignore any login shell environment | daemon.sh -f absolute_path_to_rcscript -E- |
Note: On SLES12+ or RHEL7+, the daemon.sh option '-f' will create and enable a
systemd service. Your daemon will only be started/stopped correctly if the corresponding
systemd service is in 'active' state. In order to turn a service into 'active' state, you need
to reboot the system or start the service with the command 'systemctl start SERVICE', where
SERVICE is the basename of the systemd service file. You can see all your systemd service
files with the command 'daemon.sh -L' (left column).