Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EFEBA200CF4 for ; Fri, 21 Jul 2017 08:41:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EE9B416CB66; Fri, 21 Jul 2017 06:41:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 597E716CB5E for ; Fri, 21 Jul 2017 08:41:16 +0200 (CEST) Received: (qmail 88078 invoked by uid 500); 21 Jul 2017 06:41:14 -0000 Mailing-List: contact commits-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list commits@geode.apache.org Received: (qmail 87851 invoked by uid 99); 21 Jul 2017 06:41:14 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jul 2017 06:41:14 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 76AC4F328C; Fri, 21 Jul 2017 06:41:13 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: zhouxj@apache.org To: commits@geode.apache.org Date: Fri, 21 Jul 2017 06:41:22 -0000 Message-Id: <1dcedf4c8bf34907b179d3d18a7cb443@git.apache.org> In-Reply-To: <6fc982108f3b4480af479ac3f3f977d0@git.apache.org> References: <6fc982108f3b4480af479ac3f3f977d0@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [10/50] [abbrv] geode git commit: GEODE-2594 Remove tools.jar and --pid options from docs archived-at: Fri, 21 Jul 2017 06:41:18 -0000 GEODE-2594 Remove tools.jar and --pid options from docs This closes #635 Project: http://git-wip-us.apache.org/repos/asf/geode/repo Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/e20873de Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/e20873de Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/e20873de Branch: refs/heads/feature/GEM-1483 Commit: e20873de5d7076f840f34bab74930946c9a30488 Parents: 43d98e0 Author: Karen Miller Authored: Thu Jul 13 17:00:53 2017 -0700 Committer: Karen Miller Committed: Fri Jul 14 13:17:08 2017 -0700 ---------------------------------------------------------------------- .../running/running_the_cacheserver.html.md.erb | 2 +- .../running/running_the_locator.html.md.erb | 4 +- .../jmx_manager_operations.html.md.erb | 4 +- .../gfsh/command-pages/start.html.md.erb | 40 ------------------ .../gfsh/command-pages/status.html.md.erb | 44 ++------------------ .../gfsh/command-pages/stop.html.md.erb | 39 +++-------------- .../gfsh/configuring_gfsh.html.md.erb | 3 -- .../gfsh/starting_gfsh.html.md.erb | 2 - 8 files changed, 14 insertions(+), 124 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/geode/blob/e20873de/geode-docs/configuring/running/running_the_cacheserver.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/configuring/running/running_the_cacheserver.html.md.erb b/geode-docs/configuring/running/running_the_cacheserver.html.md.erb index 374839b..837cf7d 100644 --- a/geode-docs/configuring/running/running_the_cacheserver.html.md.erb +++ b/geode-docs/configuring/running/running_the_cacheserver.html.md.erb @@ -31,7 +31,7 @@ The Geode server is used primarily for hosting long-lived data regions and for r The `gfsh` utility uses a working directory for its configuration files and log files. These are the defaults and configuration options: -- When you start a standalone server using `gfsh`, `gfsh` will automatically load the required JAR files `$GEMFIRE/lib/server-dependencies.jar` and `$JAVA_HOME/lib/tools.jar` into the CLASSPATH of the JVM process. If you start a standalone server using the ServerLauncher API, you must specify `$GEMFIRE/lib/server-dependencies.jar` inside your command to launch the process. For more information on CLASSPATH settings in Geode, see [Setting Up the CLASSPATH](../../getting_started/setup_classpath.html). +- When you start a standalone server using `gfsh`, `gfsh` will automatically load the required JAR file `$GEMFIRE/lib/server-dependencies.jar` into the CLASSPATH of the JVM process. If you start a standalone server using the ServerLauncher API, you must specify `$GEMFIRE/lib/server-dependencies.jar` inside your command to launch the process. For more information on CLASSPATH settings in Geode, see [Setting Up the CLASSPATH](../../getting_started/setup_classpath.html). - Servers are configured like any other Geode process, with `gemfire.properties` and shared cluster configuration files. It is not programmable except through application plug-ins. Typically, you provide the `gemfire.properties` file and the `gfsecurity.properties` file (if you are using a separate, restricted access security settings file). You can also specify a `cache.xml` file in the cache server’s working directory. - By default, a new server started with `gfsh` receives its initial cache configuration from the cluster configuration service, assuming the locator is running the cluster configuration service. If you specify a group when starting the server, the server also receives configurations that apply to a group. The shared configuration consists of `cache.xml` files, `gemfire.properties` files, and deployed jar files. You can disable use of the cluster configuration service by specifying `--use-cluster-configuration=false` when starting the server using `gfsh`. http://git-wip-us.apache.org/repos/asf/geode/blob/e20873de/geode-docs/configuring/running/running_the_locator.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/configuring/running/running_the_locator.html.md.erb b/geode-docs/configuring/running/running_the_locator.html.md.erb index 252d7e3..7d29646 100644 --- a/geode-docs/configuring/running/running_the_locator.html.md.erb +++ b/geode-docs/configuring/running/running_the_locator.html.md.erb @@ -35,7 +35,7 @@ You can run the locator standalone or embedded within another Geode process. Run Locator configuration and log files have the following properties: -- When you start a standalone locator using `gfsh`, `gfsh` will automatically load the required JAR files (`$GEMFIRE/lib/locator-dependencies.jar`) into the CLASSPATH of the JVM process. If you start a standalone locator using the `LocatorLauncher` API, you must specify `$GEMFIRE/lib/locator-dependencies.jar` inside the command used to launch the locator process. For more information on CLASSPATH settings in Geode, see [CLASSPATH Settings for Geode Processes](../../getting_started/setup_classpath.html). You can modify the CLASSPATH by specifying the `--classpath` parameter. +- When you start a standalone locator using `gfsh`, `gfsh` will automatically load the required JAR file (`$GEMFIRE/lib/locator-dependencies.jar`) into the CLASSPATH of the JVM process. If you start a standalone locator using the `LocatorLauncher` API, you must specify `$GEMFIRE/lib/locator-dependencies.jar` inside the command used to launch the locator process. For more information on CLASSPATH settings in Geode, see [CLASSPATH Settings for Geode Processes](../../getting_started/setup_classpath.html). You can modify the CLASSPATH by specifying the `--classpath` parameter. - Locators are members of the distributed system just like any other member. In terms of `mcast-port` and `locators` configuration, a locator should be configured in the same manner as a server. Therefore, if there are two other locators in the distributed system, each locator should reference the other locators (just like a server member would). For example: ``` pre @@ -218,7 +218,7 @@ Java Version: 1.7.0_65 Log File: /home/user/locator1/locator1.log JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 -Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar:/usr/local/java/lib/tools.jar +Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar Cluster configuration service is up and running. ``` http://git-wip-us.apache.org/repos/asf/geode/blob/e20873de/geode-docs/managing/management/jmx_manager_operations.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/management/jmx_manager_operations.html.md.erb b/geode-docs/managing/management/jmx_manager_operations.html.md.erb index 5ad3e23..aac909c 100644 --- a/geode-docs/managing/management/jmx_manager_operations.html.md.erb +++ b/geode-docs/managing/management/jmx_manager_operations.html.md.erb @@ -60,7 +60,7 @@ Java Version: 1.7.0_65 Log File: /home/user/test2/locator1/locator1.log JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 -Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar:/usr/local/java/lib/tools.jar +Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar Successfully connected to: [host=ubuntu.local, port=1099] @@ -80,7 +80,7 @@ Java Version: 1.7.0_65 Log File: /home/user/locator1/locator1.log JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 -Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar:/usr/local/java/lib/tools.jar +Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar Successfully connected to: [host=ubuntu.local, port=1099] http://git-wip-us.apache.org/repos/asf/geode/blob/e20873de/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb index 0044b9e..17fefa5 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb @@ -421,28 +421,6 @@ See Overview of start locator --name=locator1 ``` -**Sample Output:** - -``` pre -gfsh>start locator --name=locator3 -Starting a GemFire Locator in /home/user/locator3... -................................ -Locator in /home/user/locator3 on ubuntu.local[10334] as locator3 is currently online. -Process ID: 1898 -Uptime: 19 seconds -GemFire Version: 8.0.0 -Java Version: 1.7.0_65 -Log File: /home/user/locator3/locator3.log -JVM Arguments: -Dgemfire.default.locators=192.0.2.3[40402] --Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false --Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true --Dsun.rmi.dgc.server.gcInterval=9223372036854775806 -Class-Path: /home/user/Pivotal_GemFire_800_b48258_Linux/lib/locator-dependencies.jar: -/usr/local/java/lib/tools.jar - -Cluster configuration service is up and running. -``` - ## start pulse Launch the Geode Pulse monitoring dashboard tool in the user's default system browser and navigates the user to the landing page (login page). @@ -790,21 +768,3 @@ the cluster. gfsh>start server --name=server1 gfsh>start server --name=server2 --server-port=40405 ``` - -**Sample Output:** - -``` pre -gfsh>start server --name=server1 --server-port=40406 -Starting a GemFire Server in /home/user/server1... -.................................................... -Server in /home/user/server1 on ubuntu.local[40406] as server1 is currently online. -Process ID: 32209 -Uptime: 47 seconds -GemFire Version: 8.0.0 -Java Version: 1.7.0_65 -Log File: /home/user/server1/server1.log -JVM Arguments: -Dgemfire.default.locators=192.0.2.4[40402] -Dgemfire.use-cluster-configuration=true --XX:OnOutOfMemoryError="kill -9 %p" -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true --Dsun.rmi.dgc.server.gcInterval=9223372036854775806 -Class-Path: /home/user/Pivotal_GemFire_800_b48258_Linux/lib/server-dependencies.jar:/usr/local/java/lib/tools.jar -``` http://git-wip-us.apache.org/repos/asf/geode/blob/e20873de/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb index cd64062..01e4874 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb @@ -207,13 +207,12 @@ The status will be one of the following: - offline - not responding -**Availability:** Online or offline. If you want to obtain the status of a locator while you are offline, use the `--dir` or the `--pid` parameter. +**Availability:** Online or offline. If you want to obtain the status of a locator while you are offline, use the `--dir` option. **Syntax:** ``` pre -status locator [--name=value] [--host=value] [--port=value] -[--pid=value] [--dir=value] +status locator [--name=value] [--host=value] [--port=value] [--dir=value] ``` @@ -223,7 +222,6 @@ status locator [--name=value] [--host=value] [--port=value] | ‑‑name | Name/ID of the locator for which to display status. You must be connected to the JMX Manager to use this option. Can be used to obtain status of remote locators. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |   | | \\-\\-host | Hostname or IP address on which the Locator is running. |   | | \\-\\-port | Port on which the locator is listening. | 10334 | -| \\-\\-pid | Process ID (PID) of the running locator. |   | | \\-\\-dir | Directory in which the locator was started. | current directory | Table 3. Status Locator Parameters @@ -235,33 +233,16 @@ status locator status locator --name=locator1 ``` -**Sample Output:** - -``` pre -gfsh>status locator --name=locator1 -Locator in /home/user/gemfire/locator1 on ubuntu.local[10334] as locator1 is currently online. -Process ID: 2401 -Uptime: 12 minutes 3 seconds -GemFire Version: 8.0.0 -Java Version: 1.7.0_65 -Log File: /home/user/gemfire/locator1/locator1.log -JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false --Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 -Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar:/usr/local/java/lib/tools.jar - -Cluster configuration service is up and running. -``` - ## status server Display the status of the specified Geode cache server. -**Availability:** Online or offline. If you want to obtain the status of a server while you are offline, use the `--dir` or the `--pid` parameter. +**Availability:** Online or offline. If you want to obtain the status of a server while you are offline, use the `--dir` option. **Syntax:** ``` pre -status server [--name=value] [--pid=value] [--dir=value] +status server [--name=value] [--dir=value] ``` @@ -269,7 +250,6 @@ status server [--name=value] [--pid=value] [--dir=value] | Name | Description | Default Value | |----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | ‑‑name | Name or ID of the Cache Server for which to display status. You must be connected to the JMX Manager to use this option. Can be used to obtain status of remote servers. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |   | -| \\-\\-pid | Process ID (PID) of the running Geode Cache Server. |   | | \\-\\-dir | Directory in which the Geode Cache Server was started. | current directory | Table 4. Status Server Parameters @@ -280,19 +260,3 @@ status server [--name=value] [--pid=value] [--dir=value] status server status server --name=server1 ``` - -**Sample Output:** - -``` pre -gfsh>status server --name=server1 -Server in /home/user/gemfire/server1 on ubuntu.local[40404] as server1 is currently online. -Process ID: 2726 -Uptime: 1 minute 3 seconds -GemFire Version: 8.0.0 -Java Version: 1.7.0_65 -Log File: /home/user/gemfire/server1/server1.log -JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334] -Dgemfire.use-cluster-configuration=true - -XX:OnOutOfMemoryError="kill -9 %p" -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true --Dsun.rmi.dgc.server.gcInterval=9223372036854775806 -Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/server-dependencies.jar:/usr/local/java/lib/tools.jar -``` http://git-wip-us.apache.org/repos/asf/geode/blob/e20873de/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb index 5ba621e..e9d5820 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb @@ -146,13 +146,12 @@ pc13(5192):14622 | OK | GatewaySender ln is stopped on member pc13(5192 Stop a locator. -**Availability:** Online or offline. If you want to stop a locator while you are offline, use the `--dir` or the `--pid` parameter. +**Availability:** Online or offline. If you want to stop a locator while you are offline, use the `--dir` option. **Syntax:** ``` pre -stop locator [--name=value] [--host=value] [--port=value] [--pid=value] -[--dir=value] +stop locator [--name=value] [--host=value] [--port=value] [--dir=value] ``` @@ -160,7 +159,6 @@ stop locator [--name=value] [--host=value] [--port=value] [--pid=value] | Name | Description | Default Value | |----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | ‑‑name | The Geode member name or id of the Locator to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote locators. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |   | -| \\-\\-pid | The process id (PID) of the running Locator. |   | | \\-\\-dir | Directory in which the Locator was started. | current directory | Table 3. Stop Locator Parameters @@ -168,32 +166,19 @@ stop locator [--name=value] [--host=value] [--port=value] [--pid=value] **Example Commands:** ``` pre -stop locator [--name=value] [--host=value] [--port=value] [--pid=value] -[--dir=value] -``` - -**Sample Output:** - -``` pre -gfsh>stop locator --pid=2401 -Stopping Locator running in /home/user/gemfire/locator1 on ubuntu.local[10334] as locator1... -Process ID: 2401 -Log File: /home/user/gemfire/locator1/locator1.log -.... -No longer connected to ubuntu.local[1099]. -gfsh> +stop locator [--name=value] [--host=value] [--port=value] [--dir=value] ``` ## stop server Stop a Geode cache server. -**Availability:** Online or offline. If you want to stop a cache server while you are offline, use the `--dir` or the `--pid` parameter. +**Availability:** Online or offline. If you want to stop a cache server while you are offline, use the `--dir` option. **Syntax:** ``` pre -stop server [--name=value] [--pid=value] [--dir=value] +stop server [--name=value] [--dir=value] ``` @@ -201,7 +186,6 @@ stop server [--name=value] [--pid=value] [--dir=value] | Name | Description | Default Value | |-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | ‑‑name | Name/Id of the Geode Cache Server to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote servers. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |   | -| \\-\\-pid | Process ID (PID) of the running Geode Cache Server. |   | | \\-\\-dir | Directory in which the Geode Cache Server was started. | current directory | Table 4. Stop Server Parameters @@ -211,17 +195,4 @@ stop server [--name=value] [--pid=value] [--dir=value] ``` pre stop server --name=server1 stop server --dir=server1 -stop server --pid=8540 -``` - -**Sample Output:** - -``` pre -gfsh>stop server --pid=2726 -Stopping Cache Server running in /home/user/gemfire/server1 on ubuntu.local[40404] as server1... -Process ID: 2726 -Log File: /home/user/gemfire/server1/server1.log -.... ``` - - http://git-wip-us.apache.org/repos/asf/geode/blob/e20873de/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb b/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb index b112e66..6000610 100644 --- a/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb +++ b/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb @@ -28,9 +28,6 @@ When you start up `gfsh`, it will automatically load required JAR files that hav These dependency JAR files are packaged in your Apache Geode installation in the `$GEMFIRE/lib` (or on Windows, the `%GEODE_HOME%\lib`) directory. -**Note:** -The `gfsh` command-line utility also searches for `tools.jar` (included with JDK) and adds it to gfsh's CLASSPATH. If you do not have a JDK installed, gfsh uses file-based communication instead for the `status` and `stop` commands. If using a JRE instead of JDK, gfsh must have read-write permissions in the working directory of the server and locator processes. - ## Machine Hostname On some operating systems, you may need to ensure that the hostname of your machine is configured in your system hosts file. For example, on Mac OSX you may need to map your machine's hostname to your IP address in the `/etc/hosts` file in order for `gfsh` and Pulse to operate correctly. http://git-wip-us.apache.org/repos/asf/geode/blob/e20873de/geode-docs/tools_modules/gfsh/starting_gfsh.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/tools_modules/gfsh/starting_gfsh.html.md.erb b/geode-docs/tools_modules/gfsh/starting_gfsh.html.md.erb index b123795..21b22a2 100644 --- a/geode-docs/tools_modules/gfsh/starting_gfsh.html.md.erb +++ b/geode-docs/tools_modules/gfsh/starting_gfsh.html.md.erb @@ -21,8 +21,6 @@ limitations under the License. Before you start gfsh, confirm that you have set JAVA\_HOME and that your PATH variable includes the gfsh executable. -To manage servers and locators properly, `gfsh` requires the `tools.jar` file (provided with the JDK) exist in the CLASSPATH. - **Note:** On Windows, you must have the JAVA\_HOME environment variable set properly to use start, stop and status commands for both locators and servers.