summaryrefslogtreecommitdiff
path: root/doc/installation.md
diff options
context:
space:
mode:
authorPaul Bütow <pbuetow@mimecast.com>2020-01-23 11:48:42 +0000
committerPaul Bütow <pbuetow@mimecast.com>2020-01-23 11:48:42 +0000
commit2a8e5de265a0e0a31a5834909d6879f5c9941467 (patch)
treec72761ce6c31937778cd1cbaff6f76b1dc2acb25 /doc/installation.md
parentce1663bacc1c83983ba9e4446d07b6d79d004b9c (diff)
parenteee041d58738f17f97db4b4302ea77086ff8f5ac (diff)
Merge branch 'master' into develop
Diffstat (limited to 'doc/installation.md')
-rw-r--r--doc/installation.md18
1 files changed, 8 insertions, 10 deletions
diff --git a/doc/installation.md b/doc/installation.md
index d1ecf9f..305eae5 100644
--- a/doc/installation.md
+++ b/doc/installation.md
@@ -5,11 +5,9 @@ The following installation guide has been tested successfully on CentOS 7. You m
This guide also assumes that you know how to use ``systemd`` and how to configure a service there. If you are unsure please consult the documentation of your distribution.
-This guide also assumes that you know how to add a new Nagios check to your monitoring infrastructure.
-
# Compile it
-Please check the [Quick Starting Guide](quickstart.md) for instructions how to compile DTail. It is recommended to automate the build process via your build pipeline (e.g. produce a deployable RPM via Jenkins). But that is out of scope of this documentation.
+Please check the [Quick Starting Guide](quickstart.md) for instructions how to compile DTail. It is recommended to automate the build process via your build pipeline (e.g. produce a deployable RPM via Jenkins). You don't have to use ``go get...`` to compile and install the binaries. You can also clone the repository and use ``make`` instead.
# Install it
@@ -17,22 +15,22 @@ It is recommended to automate all the installation process outlined here. You co
1. The ``dserver`` binary has to be installed on all machines (server boxes) involved. A good location for the binary would be ``/usr/local/bin/dserver`` with permissions set as follows:
```console
-serv-001 ~ % sudo chown root:root /usr/local/bin/dserver
-serv-001 ~ % sudo chmod 0755 /usr/local/bin/dserver
+% sudo chown root:root /usr/local/bin/dserver
+% sudo chmod 0755 /usr/local/bin/dserver
```
2. Create the ``dserver`` run user and group. The user could look like this:
```console
-serv-001 ~ % id dserver
+% id dserver
uid=670(dserver) gid=670(dserver) groups=670(dserver)
```
3. Create the required file system structure and set the correct permissions:
```console
-serv-001 ~ % sudo mkdir -p /etc/dserver /var/run/dserver
-serv-001 ~ % sudo chown -R dserver:dserver /var/run/dserver
+% sudo mkdir -p /etc/dserver /var/run/dserver
+% sudo chown -R dserver:dserver /var/run/dserver
```
4. Install the ``dtail.json`` config to ``/etc/dserver/dtail.json``. An example can be found [here](../samples/dtail.json.sample).
@@ -44,8 +42,8 @@ serv-001 ~ % sudo chown -R dserver:dserver /var/run/dserver
To start the DTail server via ``systemd`` run:
```console
-serv-001 ~ % sudo systemctl start dserver
-serv-001 ~ % sudo systemctl status dserver
+% sudo systemctl start dserver
+% sudo systemctl status dserver
● dserver.service - DTail server
Loaded: loaded (/etc/systemd/system/dserver.service; disabled; vendor preset: disabled)
Active: active (running) since Fri 2019-12-06 13:21:24 GMT; 2s ago