From bc367ac44dafc4468f673615e5e09ee95293d870 Mon Sep 17 00:00:00 2001 From: Arthur Nascimento Date: Thu, 7 Sep 2023 15:33:50 -0300 Subject: [PATCH] Update 06_configuring_for_eager_failover.mdx The safest way for end users to edit service files is using `systemctl edit`. Alternatively, we can instruct them on how to edit the overrides files in `/etc/systemd/system/.d/override.conf`. But creating a new file and `.include` shouldn't have been an option. Moreover, the `.include` feature has been removed from recent systemd versions, so it must be changed before it starts erroring out in the customer's hands. --- .../06_configuring_for_eager_failover.mdx | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx index 5d55cccb262..af73de8805b 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx @@ -29,18 +29,17 @@ You can set up Eager Failover by performing the following steps. The example us - Ensure that the database server and the local Failover Manager agent are running. -- As root, create `/etc/systemd/system/edb-as-12.service` file and include: +- As root, edit the service `edb-as-12.service` file using the command: - ```ini - .include /lib/systemd/system/edb-as-12.service - [Unit] - BindsTo=edb-efm-4.5.service + ```shell + systemctl edit edb-as-12.service ``` -- Run the following command to reload the configuration files: +- Add the following lines into the text editor, then save: - ```shell - systemctl daemon-reload + ```ini + [Unit] + BindsTo=edb-efm-4.5.service ``` With these changes, when the Failover Manager agent is stopped or ended, the rest of the cluster treats this situation as a failure and attempts a failover.