Adding Dependencies to systemd Unit Configuration Files

If your system supports systemd before you can safely reboot your protected host or use the files in the GuardPoint, you must perform the following steps to set the proper CTE dependencies for your applications.

1. Compile a list of your applications that use GuardPoints.

2. Prepare users of those applications for the interruption in service required to make these changes.

3. Shut down each of the affected applications.

4. For each application, log in as root and open the unit configuration file for that application using a text editor such as vi. See the table above to determine the location of the systemd unit file.

   For example, the unit configuration file for a hypothetical exampled application would be located in /usr/lib/systemd/system/exampled.service.

5. Locate the [Unit] area in the file and add the following two lines at the end of the [Unit] section:

   After=secfs-fuse.service
BindsTo=secfs-fuse.service

   • After=secfs-fuse.service

     • Ensures that the current service, for example NFS service, starts only after secfs-fuse.service starts.       
     • Does not create any dependency on the secfs-fuse service, and doesn't fail if secfs-fuse service fails to start or is not running.

   • BindsTo=secfs-fuse.service       

     • Creates a strong dependency on secfs-fuse.service.

     • If secfs-fuse.service stops or fails, the current service stops as well.

6. Save and close the unit configuration file.

7. Repeat steps 3–6 for each application.

Continue to Adding Applications to the secfs-fuse.service File to make necessary changes to secfs-fs-barrier.service.