[
https://issues.apache.org/jira/browse/GEODE-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989558#comment-15989558
]
ASF GitHub Bot commented on GEODE-2850:
---------------------------------------
GitHub user davebarnes97 opened a pull request:
https://github.com/apache/geode/pull/482
gfsh help now uses log4j log levels: update user guide
Where gfsh documentation listed log level params, replaced the "old" levels
(fine, finer, finest, etc) with log4j levels (ALL, TRACE, DEBUG, etc).
Did not replace log level params in non-gfsh contexts (e.g. Java command
lines or xml config files).
Also did not standardize "loglevel" vs "log-level", which are
inconsistently used in the gfsh interface (see GEODE-2850).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davebarnes97/geode feature/GEODE-2778
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode/pull/482.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #482
----
commit 29177fed58851868c698f9c24c7424903ea22461
Author: Dave Barnes <dbar...@pivotal.io>
Date: 2017-04-28T22:55:50Z
gfsh help now uses log4j log levels: update user guide
----
> gfsh commands accepting log level options use inconsistent syntax
> -----------------------------------------------------------------
>
> Key: GEODE-2850
> URL: https://issues.apache.org/jira/browse/GEODE-2850
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
> Reporter: Dave Barnes
> Assignee: Kirk Lund
>
> Some gfsh commands accept "--loglevel", others require "--log-level".
> For example,
> "change loglevel" insists on --loglevel=value
> "start server" seems to accept both --loglevel and --log-level
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
