CTE Configuration Changes Required on systemd
The following table is a high-level overview of the required changes in systemd unit configuration files to control the applications that must be in sync with CTE during system startup and shutdown.
Typical applications that require systemd changes include postgres, httpd, mongodb, mysqld and mariadb. For example, mongodb requires that CTE to be running before mongodb starts.
Caution
Configuring the dependencies as recommended here mean that whenever you stop CTE or if CTE stops unexpectedly, the dependent applications will automatically stop shortly before CTE stops. Be sure you understand the implications of this behavior on your production environment.
| Task | For more information |
|---|---|
| Compile a list of your applications that use GuardPoints. | See the application examples above. |
| Shut down the applications that use GuardPoints. | Adding Dependencies to systemd Unit Configuration Files |
Add the following lines to the [Unit] section of the systemd unit configuration file for each application:After=secfs-fs-barrier.serviceBindsTo=secfs-fs-barrier.service |
Adding Dependencies to systemd Unit Configuration Files |
To the Before= line in the [Unit] section of the secfs-fs-barrier.service file, add the following:saslauthd.serviceAn entry for each application you added to the systemd unit configuration file. |
Adding Applications to the secfs-fs-barrier.service File |
Add the following lines to the [Unit] section of the saslauthd.service configuration file:BindsTo=secfs-fs-barrier.serviceAfter=secfs-fs-barrier.service |
Adding Dependencies to the saslauthd.service File |
Force the system to read the changed systemd configuration files by typing systemctl daemon-reload. |
Adding Dependencies to the saslauthd.service File |
| Restart the applications that you shut down to make these changes. | Adding Dependencies to the saslauthd.service File |
