From d33e4716f006e50fc9ba0ac9b1489ed96c234119 Mon Sep 17 00:00:00 2001
From: Tamas Gal <tgal@km3net.de>
Date: Thu, 23 May 2019 01:05:53 +0200
Subject: [PATCH] Update README.md
---
README.md | 34 ++++++++++++++++++++++++++++++++--
1 file changed, 32 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index de540f5..a2061af 100644
--- a/README.md
+++ b/README.md
@@ -32,17 +32,47 @@ export TAGS_TO_MIRROR="IO_EVT, IO_SUM, IO_TSL, IO_TSL0, IO_TSL1, IO_TSL2, IO_TSS
```
-After that, use the following command to start the ``supervisor``:
+After that, use the following command to start the ``supervisor``, which
+you only need to do once:
source setenv.sh
make start
-To see the status of the processes, use ``supervisorctl status``
+From now on ``supervisorctl`` is the tool to communicate with the monitoring
+system. To see the status of the processes, use ``supervisorctl status``,
+which will show each process one by one (make sure you call it in the
+folder where you launched it):
+```
+$ supervisorctl status
+ligiers:ligiermirror RUNNING pid 611, uptime 1 day, 7:55:09
+ligiers:monitoring_ligier RUNNING pid 610, uptime 1 day, 7:55:09
+logging:msg_dumper RUNNING pid 7466, uptime 1 day, 7:28:00
+logging:weblog RUNNING pid 7465, uptime 1 day, 7:28:00
+monitoring_process:ahrs_calibration RUNNING pid 19612, uptime 1 day, 1:20:32
+monitoring_process:dom_activity RUNNING pid 626, uptime 1 day, 7:55:09
+monitoring_process:dom_rates RUNNING pid 631, uptime 1 day, 7:55:09
+monitoring_process:pmt_hrv RUNNING pid 633, uptime 1 day, 7:55:09
+monitoring_process:pmt_rates RUNNING pid 632, uptime 1 day, 7:55:09
+monitoring_process:rttc RUNNING pid 9717, uptime 10:55:53
+monitoring_process:trigger_rates RUNNING pid 637, uptime 1 day, 7:55:09
+monitoring_process:triggermap RUNNING pid 638, uptime 1 day, 7:55:09
+monitoring_process:ztplot RUNNING pid 7802, uptime 1 day, 7:26:13
+webserver RUNNING pid 29494, uptime 1 day, 0:34:23
+```
+
+The processes are grouped accordingly (ligier, monitoring_process etc.) and
+automaticallly started in the right order.
You can stop and start individual services using ``supervisorctl stop
group:process_name`` and ``supervisorctl start group:process_name``
+Since the system knows the order, you can safely ``restart all`` or just
+a group of processes. Use the ``supervisorctl help`` to find out more and
+``supervisorctl help COMMAND`` to get a detailed description of the
+corresponding command.
+
+
## Configuration file
A file called `pipeline.toml` can be placed into the root folder of the
--
GitLab