From b4883d4a1cf9d0a07ec12279d4a115a237d766ba Mon Sep 17 00:00:00 2001 From: Elastic Jasper Date: Thu, 6 Oct 2016 14:59:25 -0400 Subject: [PATCH] Backport PR #8483 --------- **Commit 1:** Doc error: bin/kibana plugin doesn't restart Kibana! * Original sha: 7c0ff89179c1034899885214a4bd697ee024ee16 * Authored by Sina Sheikholeslami on 2016-09-27T15:02:13Z * Committed by GitHub on 2016-09-27T15:02:13Z **Commit 2:** Applied requested changes. Since the process of restarting Kibana varies from OS to OS, I've included the means to restart it on Ubuntu machines as an example. * Original sha: 488d0cb20ea1ead621daeb3801875c169a9e592f * Authored by Sina Sheikholeslami on 2016-09-30T12:35:23Z * Committed by GitHub on 2016-09-30T12:35:23Z --- docs/plugins.asciidoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/plugins.asciidoc b/docs/plugins.asciidoc index b4ff08e6d1d5a..589b038594dea 100644 --- a/docs/plugins.asciidoc +++ b/docs/plugins.asciidoc @@ -92,8 +92,7 @@ bin/kibana plugin --install username/sample-plugin --timeout 1m ==== Plugins and Custom Kibana Configurations Use the `-c` or `--config` options to specify the path to the configuration file used to start Kibana. By default, Kibana -uses the configuration file `config/kibana.yml`. When you change your installed plugins, the `bin/kibana plugin` command -restarts the Kibana server. When you are using a customized configuration file, you must specify the +uses the configuration file `config/kibana.yml`. After you have changed the configuration file, you have to restart the Kibana server for changes to take effect (e.g. if Kibana is installed on an Ubuntu machine, you can restart it using `service kibana stop` followed by `service kibana start`). When you are using a customized configuration file, you must specify the path to that configuration file each time you use the `bin/kibana plugin` command. [float]