KITAITI Makoto
null+****@clear*****
Sun Jan 24 01:15:59 JST 2016
KITAITI Makoto 2016-01-24 01:15:59 +0900 (Sun, 24 Jan 2016) New Revision: fc90e489d32e8c2a0acac5ffddc1234d4446c0dc https://github.com/droonga/droonga.org/commit/fc90e489d32e8c2a0acac5ffddc1234d4446c0dc Merged 41d1816: Merge pull request #27 from KitaitiMakoto/systemd Message: Use systemctl command instead of service command Modified files: install/index.md reference/1.1.2/command-line-tools/droonga-engine-configure/index.md tutorial/1.1.2/add-replica/index.md tutorial/1.1.2/basic/index.md tutorial/1.1.2/benchmark/index.md tutorial/1.1.2/groonga/index.md Modified: install/index.md (+5 -5) =================================================================== --- install/index.md 2015-12-05 18:18:37 +0900 (532f514) +++ install/index.md 2016-01-24 01:15:59 +0900 (9ba0bf6) @@ -19,13 +19,13 @@ Download them and run it by `bash`, as the root: bash ~~~ -After services are installed, you can run/stop them via the `service` command: +After services are installed, you can run/stop them via the `systemctl` command: ~~~ -# service droonga-engine start -# service droonga-engine stop -# service droonga-http-server start -# service droonga-http-server stop +# systemctl start droonga-engine +# systemctl stop droonga-engine +# systemctl start droonga-http-server +# systemctl stop droonga-http-server ~~~ Now you are ready for building your own data processing system with Droonga. See [tutorial](/tutorial/) to get started. Modified: reference/1.1.2/command-line-tools/droonga-engine-configure/index.md (+3 -3) =================================================================== --- reference/1.1.2/command-line-tools/droonga-engine-configure/index.md 2015-12-05 18:18:37 +0900 (93e0f5b) +++ reference/1.1.2/command-line-tools/droonga-engine-configure/index.md 2016-01-24 01:15:59 +0900 (0f46f9d) @@ -92,15 +92,15 @@ If the `droonga-engine` service is correctly registered as a service, this comma `--daemon`, `--no-daemon` : Run as a daemon or a regular process. - However, the `droonga-engine` service always started as a daemon by the command line `service droonga-engine start`, even if these options are given. + However, the `droonga-engine` service always started as a daemon by the command line `systemctl start droonga-engine`, even if these options are given. `--pid-file=PATH` : Path to put the process ID of the daemon process. - However, the process ID of the `droonga-engine` service always stored at the platform specific location by the command line `service droonga-engine start`, even if this option is given. + However, the process ID of the `droonga-engine` service always stored at the platform specific location by the command line `systemctl start droonga-engine`, even if this option is given. `--base-dir=PATH` : Path to the directory all `droonga-engine` related files are stored into. - However, the location `/home/droonga-engine/droonga/` is always used for the `droonga-engine` service started by the command line `service droonga-engine start`, even if this option is given. + However, the location `/home/droonga-engine/droonga/` is always used for the `droonga-engine` service started by the command line `systemctl start droonga-engine`, even if this option is given. ## How to install {#install} Modified: tutorial/1.1.2/add-replica/index.md (+2 -2) =================================================================== --- tutorial/1.1.2/add-replica/index.md 2015-12-05 18:18:37 +0900 (72fe48b) +++ tutorial/1.1.2/add-replica/index.md 2016-01-24 01:15:59 +0900 (4985de1) @@ -87,8 +87,8 @@ Let's start services. ~~~ (on node2) -# service droonga-engine start -# service droonga-http-server start +# systemctl start droonga-engine +# systemctl start droonga-http-server ~~~ Currently, the new node doesn't work as a node of the existing cluster. Modified: tutorial/1.1.2/basic/index.md (+10 -10) =================================================================== --- tutorial/1.1.2/basic/index.md 2015-12-05 18:18:37 +0900 (b683008) +++ tutorial/1.1.2/basic/index.md 2016-01-24 01:15:59 +0900 (cf20690) @@ -219,22 +219,22 @@ For more details of the configuration file `catalog.json`, see [the reference ma ### Start and stop the `droonga-engine` service -The `droonga-engine` service can be started via the `service` command: +The `droonga-engine` service can be started via the `systemctl` command: ~~~ -# service droonga-engine start +# systemctl start droonga-engine ~~~ -To stop it, you also have to use the `service` command: +To stop it, you also have to use the `systemctl` command: ~~~ -# service droonga-engine stop +# systemctl stop droonga-engine ~~~ After confirmation, start the `droonga-engine` again. ~~~ -# service droonga-engine start +# systemctl start droonga-engine ~~~ ### Create a database @@ -926,22 +926,22 @@ Successfully installed droonga-http-server. ### Start and stop the `droonga-http-server` service -The `droonga-http-server` service can be started via the `service` command: +The `droonga-http-server` service can be started via the `systemctl` command: ~~~ -# service droonga-http-server start +# systemctl start droonga-http-server ~~~ -To stop it, you also have to use the `service` command: +To stop it, you also have to use the `systemctl` command: ~~~ -# service droonga-http-server stop +# systemctl stop droonga-http-server ~~~ After confirmation, start the `droonga-http-server` again. ~~~ -# service droonga-engine start +# systemctl start droonga-engine ~~~ ### Search request via HTTP Modified: tutorial/1.1.2/benchmark/index.md (+8 -8) =================================================================== --- tutorial/1.1.2/benchmark/index.md 2015-12-05 18:18:37 +0900 (9b8d38c) +++ tutorial/1.1.2/benchmark/index.md 2016-01-24 01:15:59 +0900 (0fb32e1) @@ -576,16 +576,16 @@ Before benchmarking, make your cluster with only one node. ~~~ (on node1, node2) -% sudo service droonga-engine stop -% sudo service droonga-http-server stop +% sudo systemctl stop droonga-engine +% sudo systemctl stop droonga-http-server ~~~ ~~~ (on node0) % sudo droonga-engine-catalog-generate \ --hosts=node0 -% sudo service droonga-engine restart -% sudo service droonga-http-server restart +% sudo systemctl restart droonga-engine +% sudo systemctl restart droonga-http-server ~~~ To clear effects from previous benchmark, you should restart services before each test. @@ -651,8 +651,8 @@ Before benchmarking, join the second node to the cluster. (on node0, node1) % sudo droonga-engine-catalog-generate \ --hosts=node0,node1 -% sudo service droonga-engine restart -% sudo service droonga-http-server restart +% sudo systemctl restart droonga-engine +% sudo systemctl droonga-http-server ~~~ After that both endpoints `node0` and `node1` work as a Droonga cluster with two nodes. @@ -712,8 +712,8 @@ Before benchmarking, join the last node to the cluster. (on node0, node1) % sudo droonga-engine-catalog-generate \ --hosts=node0,node1,node2 -% sudo service droonga-engine restart -% sudo service droonga-http-server restart +% sudo systemctl restart droonga-engine +% sudo systemctl restart droonga-http-server ~~~ After that all endpoints `node0`, `node1`, and `node2` work as a Droonga cluster with three nodes. Modified: tutorial/1.1.2/groonga/index.md (+5 -5) =================================================================== --- tutorial/1.1.2/groonga/index.md 2015-12-05 18:18:37 +0900 (ca1dab2) +++ tutorial/1.1.2/groonga/index.md 2016-01-24 01:15:59 +0900 (7209533) @@ -219,12 +219,12 @@ You can run Groonga as an HTTP server daemon with the option `-d`, like: On the other hand, you have to run multiple server daemons for each Droonga node to use your Droonga cluster via HTTP. -If you set up your Droonga nodes by installation scripts, daemons are already been configured as system services managed via the `service` command. +If you set up your Droonga nodes by installation scripts, daemons are already been configured as system services managed via the `systemctl` command. To start them, run commands like following on each Droonga node: ~~~ -# service droonga-engine start -# service droonga-http-server start +# systemctl start droonga-engine +# systemctl start droonga-http-server ~~~ By these commands, services start to work. @@ -279,8 +279,8 @@ Moreover, even if some `droonga-engine`s stop, `droonga-http-server` wards off t To stop services, run commands like following on each Droonga node: ~~~ -# service droonga-engine stop -# service droonga-http-server stop +# systemctl stop droonga-engine +# systemctl stop droonga-http-server ~~~ After verification, start services again, on each Droonga node. -------------- next part -------------- HTML����������������������������...Download