[
https://issues.apache.org/jira/browse/GEODE-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500350#comment-16500350
]
Barbara Pruijn commented on GEODE-2203:
---------------------------------------
If no option is specified, the output is misleading.
{code:java}
gfsh>start locator --name=l1
Starting a Geode Locator in /Users/bpruijn/geode_tmp/l1...
....
Locator in /Users/bpruijn/geode_tmp/l1 on 10.118.20.117[10334] as l1 is
currently online.
Process ID: 20034
Uptime: 5 seconds
Geode Version: 1.8.0-SNAPSHOT
Java Version: 1.8.0_151
Log File: /Users/bpruijn/geode_tmp/l1/l1.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:
/Users/bpruijn/workspace/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.8.0-SNAPSHOT.jar:/Users/bpruijn/workspace/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
Successfully connected to: JMX Manager [host=10.118.20.117, port=1099]
Cluster configuration service is up and running.
gfsh>status locator
Locator in /Users/bpruijn/geode_tmp on 10.118.20.117[10334] is currently not
responding.
gfsh>status locator --name=l1
Locator in /Users/bpruijn/geode_tmp/l1 on 10.118.20.117[10334] as l1 is
currently online.
Process ID: 20034
Uptime: 26 seconds
Geode Version: 1.8.0-SNAPSHOT
Java Version: 1.8.0_151
Log File: /Users/bpruijn/geode_tmp/l1/l1.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:
/Users/bpruijn/workspace/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.8.0-SNAPSHOT.jar:/Users/bpruijn/workspace/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
Cluster configuration service is up and running.
{code}
> gfsh status locator/server - Give more descriptive output on empty parameter
> ----------------------------------------------------------------------------
>
> Key: GEODE-2203
> URL: https://issues.apache.org/jira/browse/GEODE-2203
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
> Reporter: Alyssa Kim
> Priority: Minor
> Labels: StatusLocatorCommand, StatusServerCommand, gfsh, status
>
> Currently, executing some status commands in gfsh without valid parameters
> gives a vague explanation/output that might be misleading. Although we have
> help <command_name> for usage description, displaying 'null' as an output
> might not be the best idea.
> Current Result
> {code}
> gfsh>status locator
> null
> {code}
> {code}
> gfsh>status server
> Server in
> C:\Users\XXX\git\incubator-geode\geode-assembly\build\install\apache-geode\bin
> on null is currently not responding.
> {code}
> Improvement
> {code}
> gfsh>status locator
> SYNTAX
> status locator [--name=value] [--host=value] [--port=value] [--pid=value]
> Use help status locator to display detailed usage information
> {code}
> {code}
> gfsh>status server
> SYNTAX
> status server [--name=value] [--pid=value] [--dir=value]
> Use help status server to display detailed usage information
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
