Kentaro Hayashi
null+****@clear*****
Mon Jun 5 18:51:48 JST 2017
Kentaro Hayashi 2017-06-05 18:51:48 +0900 (Mon, 05 Jun 2017) New Revision: b824e9a83d88882c5f77e845816f2b3192a4ade4 https://github.com/groonga/groonga/commit/b824e9a83d88882c5f77e845816f2b3192a4ade4 Merged 4186302: Merge pull request #703 from kenhys/grndb-log-doc Message: doc: add log-path 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-06 11:18:47 +0900 (e1ce78a) +++ doc/source/reference/executables/grndb.rst 2017-06-05 18:51:48 +0900 (8ac80b0) @@ -94,6 +94,18 @@ Here is an example that checks only ``Entries.name`` column:: % grndb check --target Entries.name /var/lib/groonga/db/db +``--log-path`` +"""""""""""""" + +.. versionadded:: 7.0.4 + +It specifies a path of ``grndb`` log. + +Here is an example that specifies ``--log-path`` option:: + + % grndb check --log-path /var/log/groonga/grndb.log /var/lib/groonga/db/db + + ``recover`` ^^^^^^^^^^^ @@ -115,3 +127,17 @@ status. You can know whether the database is recoverable or not by You must not use this command for opened database. If the database is opened, this command may break the database. + +``recover`` has some options. + +``--log-path`` +"""""""""""""" + +.. versionadded:: 7.0.4 + +It specifies a path of ``grndb`` log. + +Here is an example that specifies ``--log-path`` option:: + + % grndb recover --log-path /var/log/groonga/grndb.log /var/lib/groonga/db/db + -------------- next part -------------- HTML����������������������������...Download