From fa48cb197d7bba98c944fd33e1293590f0dd6ba2 Mon Sep 17 00:00:00 2001 From: Jeff Huss Date: Mon, 14 Nov 2022 14:35:35 -0800 Subject: [PATCH] Fixed wording in first sentence of creating service with systemd (#1874) Signed-off-by: JeffH-AWS Signed-off-by: JeffH-AWS --- _opensearch/install/tar.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_opensearch/install/tar.md b/_opensearch/install/tar.md index 8df218d4..b973c72f 100644 --- a/_opensearch/install/tar.md +++ b/_opensearch/install/tar.md @@ -455,7 +455,7 @@ $ curl https://your.host.address:9200 -u admin:yournewpassword -k ### Run OpenSearch as a service with systemd -Create a service for OpenSearch and register it with `systemd`. After the service has been defined, you can enable, start, and stop the OpenSearch service using `systemctl` commands. The commands in this section reflect an environment where OpenSearch has been installed to `/opt/opensearch` and should be changed depending on your installation path. +This section will guide you through creating a service for OpenSearch and registering it with `systemd`. After the service has been defined, you can enable, start, and stop the OpenSearch service using `systemctl` commands. The commands in this section reflect an environment where OpenSearch has been installed to `/opt/opensearch` and should be changed depending on your installation path. The following configuration is only suitable for testing in a non-production environment. We do not recommend using the following configuration in a production environment. You should install OpenSearch with the [RPM]({{site.url}}{{site.baseurl}}/opensearch/install/rpm/) distribution if you want to run OpenSearch as a systemd-managed service on your host. The tarball installation does not define a specific installation path, users, roles, or permissions. Failure to properly secure your host environment can result in unexpected behavior. {: .warning}