Kentaro Hayashi
null+****@clear*****
Wed Jun 7 18:38:03 JST 2017
Kentaro Hayashi 2017-06-07 18:38:03 +0900 (Wed, 07 Jun 2017) New Revision: 148c3c78157b982565ae7cc8a16699deb6d727e3 https://github.com/groonga/groonga/commit/148c3c78157b982565ae7cc8a16699deb6d727e3 Merged 38a8b02: Merge pull request #708 from kenhys/grndb-log-level-doc Message: doc: add --log-level option for grndb Modified files: doc/source/reference/executables/grndb.rst Modified: doc/source/reference/executables/grndb.rst (+26 -0) =================================================================== --- doc/source/reference/executables/grndb.rst 2017-06-07 16:39:19 +0900 (8ac80b0) +++ doc/source/reference/executables/grndb.rst 2017-06-07 18:38:03 +0900 (ac90cb0) @@ -94,6 +94,19 @@ Here is an example that checks only ``Entries.name`` column:: % grndb check --target Entries.name /var/lib/groonga/db/db +``--log-level`` +""""""""""""""" + +.. versionadded:: 7.0.4 + +It specifies a log level of ``grndb`` log. + +Here is an example that specifies ``--log-level`` option:: + + % grndb check --log-level info --log-path /var/log/groonga/grndb.log /var/lib/groonga/db/db + +See :doc:`/reference/commands/log_level` to know about supported log level. + ``--log-path`` """""""""""""" @@ -130,6 +143,19 @@ status. You can know whether the database is recoverable or not by ``recover`` has some options. +``--log-level`` +""""""""""""""" + +.. versionadded:: 7.0.4 + +It specifies a log level of ``grndb`` log. + +Here is an example that specifies ``--log-level`` option:: + + % grndb recover --log-level info --log-path /var/log/groonga/grndb.log /var/lib/groonga/db/db + +See :doc:`/reference/commands/log_level` to know about supported log level. + ``--log-path`` """""""""""""" -------------- next part -------------- HTML����������������������������...下載
