[Groonga-commit] droonga/droonga.org at ff91f20 [gh-pages] Update descriptions

Back to archive index

YUKI Hiroshi null+****@clear*****
Thu May 29 16:15:11 JST 2014


YUKI Hiroshi	2014-05-29 16:15:11 +0900 (Thu, 29 May 2014)

  New Revision: ff91f20287e28594d378abf81f073fbc6a8650e4
  https://github.com/droonga/droonga.org/commit/ff91f20287e28594d378abf81f073fbc6a8650e4

  Message:
    Update descriptions

  Modified files:
    _po/ja/tutorial/1.0.3/dump-restore/index.po
    _po/ja/tutorial/1.0.3/groonga/index.po
    _po/ja/tutorial/1.0.4/dump-restore/index.po
    _po/ja/tutorial/1.0.4/groonga/index.po
    ja/tutorial/1.0.3/dump-restore/index.md
    ja/tutorial/1.0.3/groonga/index.md
    ja/tutorial/1.0.4/dump-restore/index.md
    ja/tutorial/1.0.4/groonga/index.md
    tutorial/1.0.3/dump-restore/index.md
    tutorial/1.0.3/groonga/index.md
    tutorial/1.0.4/dump-restore/index.md
    tutorial/1.0.4/groonga/index.md

  Modified: _po/ja/tutorial/1.0.3/dump-restore/index.po (+59 -6)
===================================================================
--- _po/ja/tutorial/1.0.3/dump-restore/index.po    2014-05-29 15:19:27 +0900 (9c6b2e9)
+++ _po/ja/tutorial/1.0.3/dump-restore/index.po    2014-05-29 16:15:11 +0900 (af9463c)
@@ -236,13 +236,66 @@ msgstr ""
 "やり方は単純で、単にダンプファイルを `droonga-request` コマンドを使ってからのクラスタに流し込むだけです。"
 
 msgid ""
-"For example, if your cluster is empty and constructed from two nodes `192.168."
-"0.10` and `192.168.0.11`, now your are logged in to the host `192.168.0.12`, a"
-"nd there is a dump file `dump.jsons` in the current directory, then the comman"
-"d line is:"
+"Assume that there is an empty Droonga cluster constructed from two nodes `192."
+"168.0.10` and `192.168.0.11`, now your are logged in to the host `192.168.0.12"
+"`, and there is a dump file `dump.jsons`."
+msgstr ""
+"2つのノード `192.168.0.10` と `192.168.0.11` からなる空のクラスタがあり、今 `192.168.0.12` にログインして操"
+"作を行っていて、ダンプファイルが `dump.jsons` という名前で手元にあると仮定します。"
+
+msgid ""
+"(If you are reading this tutorial sequentially, you'll have an existing cluste"
+"r and the dump file.\n"
+"Make it empty with these commands:"
+msgstr "(もし順番にこのチュートリアルを読み進めているのであれば、クラスタとダンプファイルが既に手元にあるはずです。以下の操作でクラスタを空にしましょう:"
+
+msgid ""
+"    (on 192.168.0.10)\n"
+"    # kill $(cat ~/droonga/droonga-http-server.pid)\n"
+"    # kill $(cat ~/droonga/droonga-engine.pid)\n"
+"    # rm -r ~/droonga/000\n"
+"    # host=192.168.0.10\n"
+"    # droonga-engine --host=$host \\\n"
+"                     --log-file=~/droonga/droonga-engine.log \\\n"
+"                     --daemon \\\n"
+"                     --pid-file=~/droonga/droonga-engine.pid\n"
+"    # droonga-http-server --port=10041 \\\n"
+"                          --receive-host-name=$host \\\n"
+"                          --droonga-engine-host-name=$host \\\n"
+"                          --access-log-file=~/droonga/droonga-http-server.acce"
+"ss.log \\\n"
+"                          --system-log-file=~/droonga/droonga-http-server.syst"
+"em.log \\\n"
+"                          --daemon \\\n"
+"                          --pid-file=~/droonga/droonga-http-server.pid"
+msgstr ""
+
+msgid ""
+"    (on 192.168.0.11)\n"
+"    # kill $(cat ~/droonga/droonga-http-server.pid)\n"
+"    # kill $(cat ~/droonga/droonga-engine.pid)\n"
+"    # rm -r ~/droonga/000\n"
+"    # host=192.168.0.11\n"
+"    # droonga-engine --host=$host \\\n"
+"                     --log-file=~/droonga/droonga-engine.log \\\n"
+"                     --daemon \\\n"
+"                     --pid-file=~/droonga/droonga-engine.pid\n"
+"    # droonga-http-server --port=10041 \\\n"
+"                          --receive-host-name=$host \\\n"
+"                          --droonga-engine-host-name=$host \\\n"
+"                          --access-log-file=~/droonga/droonga-http-server.acce"
+"ss.log \\\n"
+"                          --system-log-file=~/droonga/droonga-http-server.syst"
+"em.log \\\n"
+"                          --daemon \\\n"
+"                          --pid-file=~/droonga/droonga-http-server.pid"
+msgstr ""
+
+msgid "After that the cluster becomes empty.)"
+msgstr "これでクラスタは空になります。)"
+
+msgid "Then you can restore the cluster from the dump file, with a command line like:"
 msgstr ""
-"例えば、2つのノード `192.168.0.10` と `192.168.0.11` からなる空のクラスタがあり、今 `192.168.0.12` にログイ"
-"ンして操作を行っていて、ダンプファイルが `dump.jsons` という名前で手元にあるのであれば、実行するコマンドはこのようになります:"
 
 msgid ""
 "~~~\n"

  Modified: _po/ja/tutorial/1.0.3/groonga/index.po (+7 -8)
===================================================================
--- _po/ja/tutorial/1.0.3/groonga/index.po    2014-05-29 15:19:27 +0900 (1960b3d)
+++ _po/ja/tutorial/1.0.3/groonga/index.po    2014-05-29 16:15:11 +0900 (ae82498)
@@ -246,20 +246,19 @@ msgstr "サービスを起動するには、各Droongaノードで以下のよ
 msgid ""
 "    # cd ~/droonga\n"
 "    # host=192.168.0.10\n"
-"    # base_path=$PWD\n"
 "    # droonga-engine --host=$host \\\n"
-"                     --log-file=$base_path/droonga-engine.log \\\n"
+"                     --log-file=~/droonga/droonga-engine.log \\\n"
 "                     --daemon \\\n"
-"                     --pid-file=$base_path/droonga-engine.pid\n"
+"                     --pid-file=~/droonga/droonga-engine.pid\n"
 "    # droonga-http-server --port=10041 \\\n"
 "                          --receive-host-name=$host \\\n"
 "                          --droonga-engine-host-name=$host \\\n"
-"                          --access-log-file=$base_path/droonga-http-server.acc"
-"ess.log \\\n"
-"                          --system-log-file=$base_path/droonga-http-server.sys"
-"tem.log \\\n"
+"                          --access-log-file=~/droonga/droonga-http-server.acce"
+"ss.log \\\n"
+"                          --system-log-file=~/droonga/droonga-http-server.syst"
+"em.log \\\n"
 "                          --daemon \\\n"
-"                          --pid-file=$base_path/droonga-http-server.pid"
+"                          --pid-file=~/droonga/droonga-http-server.pid"
 msgstr ""
 
 msgid ""

  Modified: _po/ja/tutorial/1.0.4/dump-restore/index.po (+59 -6)
===================================================================
--- _po/ja/tutorial/1.0.4/dump-restore/index.po    2014-05-29 15:19:27 +0900 (9c6b2e9)
+++ _po/ja/tutorial/1.0.4/dump-restore/index.po    2014-05-29 16:15:11 +0900 (af9463c)
@@ -236,13 +236,66 @@ msgstr ""
 "やり方は単純で、単にダンプファイルを `droonga-request` コマンドを使ってからのクラスタに流し込むだけです。"
 
 msgid ""
-"For example, if your cluster is empty and constructed from two nodes `192.168."
-"0.10` and `192.168.0.11`, now your are logged in to the host `192.168.0.12`, a"
-"nd there is a dump file `dump.jsons` in the current directory, then the comman"
-"d line is:"
+"Assume that there is an empty Droonga cluster constructed from two nodes `192."
+"168.0.10` and `192.168.0.11`, now your are logged in to the host `192.168.0.12"
+"`, and there is a dump file `dump.jsons`."
+msgstr ""
+"2つのノード `192.168.0.10` と `192.168.0.11` からなる空のクラスタがあり、今 `192.168.0.12` にログインして操"
+"作を行っていて、ダンプファイルが `dump.jsons` という名前で手元にあると仮定します。"
+
+msgid ""
+"(If you are reading this tutorial sequentially, you'll have an existing cluste"
+"r and the dump file.\n"
+"Make it empty with these commands:"
+msgstr "(もし順番にこのチュートリアルを読み進めているのであれば、クラスタとダンプファイルが既に手元にあるはずです。以下の操作でクラスタを空にしましょう:"
+
+msgid ""
+"    (on 192.168.0.10)\n"
+"    # kill $(cat ~/droonga/droonga-http-server.pid)\n"
+"    # kill $(cat ~/droonga/droonga-engine.pid)\n"
+"    # rm -r ~/droonga/000\n"
+"    # host=192.168.0.10\n"
+"    # droonga-engine --host=$host \\\n"
+"                     --log-file=~/droonga/droonga-engine.log \\\n"
+"                     --daemon \\\n"
+"                     --pid-file=~/droonga/droonga-engine.pid\n"
+"    # droonga-http-server --port=10041 \\\n"
+"                          --receive-host-name=$host \\\n"
+"                          --droonga-engine-host-name=$host \\\n"
+"                          --access-log-file=~/droonga/droonga-http-server.acce"
+"ss.log \\\n"
+"                          --system-log-file=~/droonga/droonga-http-server.syst"
+"em.log \\\n"
+"                          --daemon \\\n"
+"                          --pid-file=~/droonga/droonga-http-server.pid"
+msgstr ""
+
+msgid ""
+"    (on 192.168.0.11)\n"
+"    # kill $(cat ~/droonga/droonga-http-server.pid)\n"
+"    # kill $(cat ~/droonga/droonga-engine.pid)\n"
+"    # rm -r ~/droonga/000\n"
+"    # host=192.168.0.11\n"
+"    # droonga-engine --host=$host \\\n"
+"                     --log-file=~/droonga/droonga-engine.log \\\n"
+"                     --daemon \\\n"
+"                     --pid-file=~/droonga/droonga-engine.pid\n"
+"    # droonga-http-server --port=10041 \\\n"
+"                          --receive-host-name=$host \\\n"
+"                          --droonga-engine-host-name=$host \\\n"
+"                          --access-log-file=~/droonga/droonga-http-server.acce"
+"ss.log \\\n"
+"                          --system-log-file=~/droonga/droonga-http-server.syst"
+"em.log \\\n"
+"                          --daemon \\\n"
+"                          --pid-file=~/droonga/droonga-http-server.pid"
+msgstr ""
+
+msgid "After that the cluster becomes empty.)"
+msgstr "これでクラスタは空になります。)"
+
+msgid "Then you can restore the cluster from the dump file, with a command line like:"
 msgstr ""
-"例えば、2つのノード `192.168.0.10` と `192.168.0.11` からなる空のクラスタがあり、今 `192.168.0.12` にログイ"
-"ンして操作を行っていて、ダンプファイルが `dump.jsons` という名前で手元にあるのであれば、実行するコマンドはこのようになります:"
 
 msgid ""
 "~~~\n"

  Modified: _po/ja/tutorial/1.0.4/groonga/index.po (+7 -8)
===================================================================
--- _po/ja/tutorial/1.0.4/groonga/index.po    2014-05-29 15:19:27 +0900 (1960b3d)
+++ _po/ja/tutorial/1.0.4/groonga/index.po    2014-05-29 16:15:11 +0900 (ae82498)
@@ -246,20 +246,19 @@ msgstr "サービスを起動するには、各Droongaノードで以下のよ
 msgid ""
 "    # cd ~/droonga\n"
 "    # host=192.168.0.10\n"
-"    # base_path=$PWD\n"
 "    # droonga-engine --host=$host \\\n"
-"                     --log-file=$base_path/droonga-engine.log \\\n"
+"                     --log-file=~/droonga/droonga-engine.log \\\n"
 "                     --daemon \\\n"
-"                     --pid-file=$base_path/droonga-engine.pid\n"
+"                     --pid-file=~/droonga/droonga-engine.pid\n"
 "    # droonga-http-server --port=10041 \\\n"
 "                          --receive-host-name=$host \\\n"
 "                          --droonga-engine-host-name=$host \\\n"
-"                          --access-log-file=$base_path/droonga-http-server.acc"
-"ess.log \\\n"
-"                          --system-log-file=$base_path/droonga-http-server.sys"
-"tem.log \\\n"
+"                          --access-log-file=~/droonga/droonga-http-server.acce"
+"ss.log \\\n"
+"                          --system-log-file=~/droonga/droonga-http-server.syst"
+"em.log \\\n"
 "                          --daemon \\\n"
-"                          --pid-file=$base_path/droonga-http-server.pid"
+"                          --pid-file=~/droonga/droonga-http-server.pid"
 msgstr ""
 
 msgid ""

  Modified: ja/tutorial/1.0.3/dump-restore/index.md (+41 -1)
===================================================================
--- ja/tutorial/1.0.3/dump-restore/index.md    2014-05-29 15:19:27 +0900 (44b3e4d)
+++ ja/tutorial/1.0.3/dump-restore/index.md    2014-05-29 16:15:11 +0900 (b05a9f6)
@@ -145,7 +145,47 @@ Droongaクラスタにそれらのメッセージを送信するには、`droong
 `drndump` の実行結果はダンプ出力元と同じ内容のデータセットを作るために必要な情報をすべて含んでいます。そのため、クラスタが壊れた場合でも、ダンプファイルからクラスタを再構築する事ができます。
 やり方は単純で、単にダンプファイルを `droonga-request` コマンドを使ってからのクラスタに流し込むだけです。
 
-例えば、2つのノード `192.168.0.10` と `192.168.0.11` からなる空のクラスタがあり、今 `192.168.0.12` にログインして操作を行っていて、ダンプファイルが `dump.jsons` という名前で手元にあるのであれば、実行するコマンドはこのようになります:
+2つのノード `192.168.0.10` と `192.168.0.11` からなる空のクラスタがあり、今 `192.168.0.12` にログインして操作を行っていて、ダンプファイルが `dump.jsons` という名前で手元にあると仮定します。
+
+(もし順番にこのチュートリアルを読み進めているのであれば、クラスタとダンプファイルが既に手元にあるはずです。以下の操作でクラスタを空にしましょう:
+
+    (on 192.168.0.10)
+    # kill $(cat ~/droonga/droonga-http-server.pid)
+    # kill $(cat ~/droonga/droonga-engine.pid)
+    # rm -r ~/droonga/000
+    # host=192.168.0.10
+    # droonga-engine --host=$host \
+                     --log-file=~/droonga/droonga-engine.log \
+                     --daemon \
+                     --pid-file=~/droonga/droonga-engine.pid
+    # droonga-http-server --port=10041 \
+                          --receive-host-name=$host \
+                          --droonga-engine-host-name=$host \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
+                          --daemon \
+                          --pid-file=~/droonga/droonga-http-server.pid
+
+    (on 192.168.0.11)
+    # kill $(cat ~/droonga/droonga-http-server.pid)
+    # kill $(cat ~/droonga/droonga-engine.pid)
+    # rm -r ~/droonga/000
+    # host=192.168.0.11
+    # droonga-engine --host=$host \
+                     --log-file=~/droonga/droonga-engine.log \
+                     --daemon \
+                     --pid-file=~/droonga/droonga-engine.pid
+    # droonga-http-server --port=10041 \
+                          --receive-host-name=$host \
+                          --droonga-engine-host-name=$host \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
+                          --daemon \
+                          --pid-file=~/droonga/droonga-http-server.pid
+
+これでクラスタは空になります。)
+
+Then you can restore the cluster from the dump file, with a command line like:
 
 ~~~
 # droonga-request --host=192.168.0.10 \

  Modified: ja/tutorial/1.0.3/groonga/index.md (+5 -6)
===================================================================
--- ja/tutorial/1.0.3/groonga/index.md    2014-05-29 15:19:27 +0900 (36282d2)
+++ ja/tutorial/1.0.3/groonga/index.md    2014-05-29 16:15:11 +0900 (b95c298)
@@ -118,18 +118,17 @@ GroongaをHTTPサーバとして使う場合は、以下のように `-d` オプ
 
     # cd ~/droonga
     # host=192.168.0.10
-    # base_path=$PWD
     # droonga-engine --host=$host \
-                     --log-file=$base_path/droonga-engine.log \
+                     --log-file=~/droonga/droonga-engine.log \
                      --daemon \
-                     --pid-file=$base_path/droonga-engine.pid
+                     --pid-file=~/droonga/droonga-engine.pid
     # droonga-http-server --port=10041 \
                           --receive-host-name=$host \
                           --droonga-engine-host-name=$host \
-                          --access-log-file=$base_path/droonga-http-server.access.log \
-                          --system-log-file=$base_path/droonga-http-server.system.log \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
                           --daemon \
-                          --pid-file=$base_path/droonga-http-server.pid
+                          --pid-file=~/droonga/droonga-http-server.pid
 
 いくつかのオプションにおいて、そのDroongaノード自身のホスト名を指定する必要がある事に注意して下さい。
 この情報は、クラスタ内の他のDroongaノードとの通信のために使われます。

  Modified: ja/tutorial/1.0.4/dump-restore/index.md (+41 -1)
===================================================================
--- ja/tutorial/1.0.4/dump-restore/index.md    2014-05-29 15:19:27 +0900 (6c7fd3e)
+++ ja/tutorial/1.0.4/dump-restore/index.md    2014-05-29 16:15:11 +0900 (f8e5d80)
@@ -145,7 +145,47 @@ Droongaクラスタにそれらのメッセージを送信するには、`droong
 `drndump` の実行結果はダンプ出力元と同じ内容のデータセットを作るために必要な情報をすべて含んでいます。そのため、クラスタが壊れた場合でも、ダンプファイルからクラスタを再構築する事ができます。
 やり方は単純で、単にダンプファイルを `droonga-request` コマンドを使ってからのクラスタに流し込むだけです。
 
-例えば、2つのノード `192.168.0.10` と `192.168.0.11` からなる空のクラスタがあり、今 `192.168.0.12` にログインして操作を行っていて、ダンプファイルが `dump.jsons` という名前で手元にあるのであれば、実行するコマンドはこのようになります:
+2つのノード `192.168.0.10` と `192.168.0.11` からなる空のクラスタがあり、今 `192.168.0.12` にログインして操作を行っていて、ダンプファイルが `dump.jsons` という名前で手元にあると仮定します。
+
+(もし順番にこのチュートリアルを読み進めているのであれば、クラスタとダンプファイルが既に手元にあるはずです。以下の操作でクラスタを空にしましょう:
+
+    (on 192.168.0.10)
+    # kill $(cat ~/droonga/droonga-http-server.pid)
+    # kill $(cat ~/droonga/droonga-engine.pid)
+    # rm -r ~/droonga/000
+    # host=192.168.0.10
+    # droonga-engine --host=$host \
+                     --log-file=~/droonga/droonga-engine.log \
+                     --daemon \
+                     --pid-file=~/droonga/droonga-engine.pid
+    # droonga-http-server --port=10041 \
+                          --receive-host-name=$host \
+                          --droonga-engine-host-name=$host \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
+                          --daemon \
+                          --pid-file=~/droonga/droonga-http-server.pid
+
+    (on 192.168.0.11)
+    # kill $(cat ~/droonga/droonga-http-server.pid)
+    # kill $(cat ~/droonga/droonga-engine.pid)
+    # rm -r ~/droonga/000
+    # host=192.168.0.11
+    # droonga-engine --host=$host \
+                     --log-file=~/droonga/droonga-engine.log \
+                     --daemon \
+                     --pid-file=~/droonga/droonga-engine.pid
+    # droonga-http-server --port=10041 \
+                          --receive-host-name=$host \
+                          --droonga-engine-host-name=$host \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
+                          --daemon \
+                          --pid-file=~/droonga/droonga-http-server.pid
+
+これでクラスタは空になります。)
+
+Then you can restore the cluster from the dump file, with a command line like:
 
 ~~~
 # droonga-request --host=192.168.0.10 \

  Modified: ja/tutorial/1.0.4/groonga/index.md (+5 -6)
===================================================================
--- ja/tutorial/1.0.4/groonga/index.md    2014-05-29 15:19:27 +0900 (0af6349)
+++ ja/tutorial/1.0.4/groonga/index.md    2014-05-29 16:15:11 +0900 (e284700)
@@ -118,18 +118,17 @@ GroongaをHTTPサーバとして使う場合は、以下のように `-d` オプ
 
     # cd ~/droonga
     # host=192.168.0.10
-    # base_path=$PWD
     # droonga-engine --host=$host \
-                     --log-file=$base_path/droonga-engine.log \
+                     --log-file=~/droonga/droonga-engine.log \
                      --daemon \
-                     --pid-file=$base_path/droonga-engine.pid
+                     --pid-file=~/droonga/droonga-engine.pid
     # droonga-http-server --port=10041 \
                           --receive-host-name=$host \
                           --droonga-engine-host-name=$host \
-                          --access-log-file=$base_path/droonga-http-server.access.log \
-                          --system-log-file=$base_path/droonga-http-server.system.log \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
                           --daemon \
-                          --pid-file=$base_path/droonga-http-server.pid
+                          --pid-file=~/droonga/droonga-http-server.pid
 
 いくつかのオプションにおいて、そのDroongaノード自身のホスト名を指定する必要がある事に注意して下さい。
 この情報は、クラスタ内の他のDroongaノードとの通信のために使われます。

  Modified: tutorial/1.0.3/dump-restore/index.md (+42 -1)
===================================================================
--- tutorial/1.0.3/dump-restore/index.md    2014-05-29 15:19:27 +0900 (34d99fe)
+++ tutorial/1.0.3/dump-restore/index.md    2014-05-29 16:15:11 +0900 (db80004)
@@ -137,7 +137,48 @@ After that, establish that the `droonga-request` command has been installed succ
 Because the result of the `drndump` command includes complete information to construct a dataset same to the source, you can re-construct your cluster from a dump file, even if the cluster is broken.
 You just have to pour the contents of the dump file to an empty cluster, by the `droonga-request` command.
 
-For example, if your cluster is empty and constructed from two nodes `192.168.0.10` and `192.168.0.11`, now your are logged in to the host `192.168.0.12`, and there is a dump file `dump.jsons` in the current directory, then the command line is:
+Assume that there is an empty Droonga cluster constructed from two nodes `192.168.0.10` and `192.168.0.11`, now your are logged in to the host `192.168.0.12`, and there is a dump file `dump.jsons`.
+
+(If you are reading this tutorial sequentially, you'll have an existing cluster and the dump file.
+Make it empty with these commands:
+
+    (on 192.168.0.10)
+    # kill $(cat ~/droonga/droonga-http-server.pid)
+    # kill $(cat ~/droonga/droonga-engine.pid)
+    # rm -r ~/droonga/000
+    # host=192.168.0.10
+    # droonga-engine --host=$host \
+                     --log-file=~/droonga/droonga-engine.log \
+                     --daemon \
+                     --pid-file=~/droonga/droonga-engine.pid
+    # droonga-http-server --port=10041 \
+                          --receive-host-name=$host \
+                          --droonga-engine-host-name=$host \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
+                          --daemon \
+                          --pid-file=~/droonga/droonga-http-server.pid
+
+    (on 192.168.0.11)
+    # kill $(cat ~/droonga/droonga-http-server.pid)
+    # kill $(cat ~/droonga/droonga-engine.pid)
+    # rm -r ~/droonga/000
+    # host=192.168.0.11
+    # droonga-engine --host=$host \
+                     --log-file=~/droonga/droonga-engine.log \
+                     --daemon \
+                     --pid-file=~/droonga/droonga-engine.pid
+    # droonga-http-server --port=10041 \
+                          --receive-host-name=$host \
+                          --droonga-engine-host-name=$host \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
+                          --daemon \
+                          --pid-file=~/droonga/droonga-http-server.pid
+
+After that the cluster becomes empty.)
+
+Then you can restore the cluster from the dump file, with a command line like:
 
 ~~~
 # droonga-request --host=192.168.0.10 \

  Modified: tutorial/1.0.3/groonga/index.md (+5 -6)
===================================================================
--- tutorial/1.0.3/groonga/index.md    2014-05-29 15:19:27 +0900 (d70e990)
+++ tutorial/1.0.3/groonga/index.md    2014-05-29 16:15:11 +0900 (23ca4cf)
@@ -109,18 +109,17 @@ To start them, run commands like following on each Droonga node:
 
     # cd ~/droonga
     # host=192.168.0.10
-    # base_path=$PWD
     # droonga-engine --host=$host \
-                     --log-file=$base_path/droonga-engine.log \
+                     --log-file=~/droonga/droonga-engine.log \
                      --daemon \
-                     --pid-file=$base_path/droonga-engine.pid
+                     --pid-file=~/droonga/droonga-engine.pid
     # droonga-http-server --port=10041 \
                           --receive-host-name=$host \
                           --droonga-engine-host-name=$host \
-                          --access-log-file=$base_path/droonga-http-server.access.log \
-                          --system-log-file=$base_path/droonga-http-server.system.log \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
                           --daemon \
-                          --pid-file=$base_path/droonga-http-server.pid
+                          --pid-file=~/droonga/droonga-http-server.pid
 
 Note that you have to specify the host name of the Droonga node itself via some options.
 It will be used to communicate with other Droonga nodes in the cluster.

  Modified: tutorial/1.0.4/dump-restore/index.md (+42 -1)
===================================================================
--- tutorial/1.0.4/dump-restore/index.md    2014-05-29 15:19:27 +0900 (34d99fe)
+++ tutorial/1.0.4/dump-restore/index.md    2014-05-29 16:15:11 +0900 (db80004)
@@ -137,7 +137,48 @@ After that, establish that the `droonga-request` command has been installed succ
 Because the result of the `drndump` command includes complete information to construct a dataset same to the source, you can re-construct your cluster from a dump file, even if the cluster is broken.
 You just have to pour the contents of the dump file to an empty cluster, by the `droonga-request` command.
 
-For example, if your cluster is empty and constructed from two nodes `192.168.0.10` and `192.168.0.11`, now your are logged in to the host `192.168.0.12`, and there is a dump file `dump.jsons` in the current directory, then the command line is:
+Assume that there is an empty Droonga cluster constructed from two nodes `192.168.0.10` and `192.168.0.11`, now your are logged in to the host `192.168.0.12`, and there is a dump file `dump.jsons`.
+
+(If you are reading this tutorial sequentially, you'll have an existing cluster and the dump file.
+Make it empty with these commands:
+
+    (on 192.168.0.10)
+    # kill $(cat ~/droonga/droonga-http-server.pid)
+    # kill $(cat ~/droonga/droonga-engine.pid)
+    # rm -r ~/droonga/000
+    # host=192.168.0.10
+    # droonga-engine --host=$host \
+                     --log-file=~/droonga/droonga-engine.log \
+                     --daemon \
+                     --pid-file=~/droonga/droonga-engine.pid
+    # droonga-http-server --port=10041 \
+                          --receive-host-name=$host \
+                          --droonga-engine-host-name=$host \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
+                          --daemon \
+                          --pid-file=~/droonga/droonga-http-server.pid
+
+    (on 192.168.0.11)
+    # kill $(cat ~/droonga/droonga-http-server.pid)
+    # kill $(cat ~/droonga/droonga-engine.pid)
+    # rm -r ~/droonga/000
+    # host=192.168.0.11
+    # droonga-engine --host=$host \
+                     --log-file=~/droonga/droonga-engine.log \
+                     --daemon \
+                     --pid-file=~/droonga/droonga-engine.pid
+    # droonga-http-server --port=10041 \
+                          --receive-host-name=$host \
+                          --droonga-engine-host-name=$host \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
+                          --daemon \
+                          --pid-file=~/droonga/droonga-http-server.pid
+
+After that the cluster becomes empty.)
+
+Then you can restore the cluster from the dump file, with a command line like:
 
 ~~~
 # droonga-request --host=192.168.0.10 \

  Modified: tutorial/1.0.4/groonga/index.md (+5 -6)
===================================================================
--- tutorial/1.0.4/groonga/index.md    2014-05-29 15:19:27 +0900 (d70e990)
+++ tutorial/1.0.4/groonga/index.md    2014-05-29 16:15:11 +0900 (23ca4cf)
@@ -109,18 +109,17 @@ To start them, run commands like following on each Droonga node:
 
     # cd ~/droonga
     # host=192.168.0.10
-    # base_path=$PWD
     # droonga-engine --host=$host \
-                     --log-file=$base_path/droonga-engine.log \
+                     --log-file=~/droonga/droonga-engine.log \
                      --daemon \
-                     --pid-file=$base_path/droonga-engine.pid
+                     --pid-file=~/droonga/droonga-engine.pid
     # droonga-http-server --port=10041 \
                           --receive-host-name=$host \
                           --droonga-engine-host-name=$host \
-                          --access-log-file=$base_path/droonga-http-server.access.log \
-                          --system-log-file=$base_path/droonga-http-server.system.log \
+                          --access-log-file=~/droonga/droonga-http-server.access.log \
+                          --system-log-file=~/droonga/droonga-http-server.system.log \
                           --daemon \
-                          --pid-file=$base_path/droonga-http-server.pid
+                          --pid-file=~/droonga/droonga-http-server.pid
 
 Note that you have to specify the host name of the Droonga node itself via some options.
 It will be used to communicate with other Droonga nodes in the cluster.
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Back to archive index