commit f76d4421870c2392f33ba93cbb95d2d860f7f4dd
parent 0958452fda58fc0cb52417cc749cc5a9ba00f1b5
Author: Nullptrderef <nullptrderef@proton.me>
Date: Sun, 4 Aug 2024 20:49:15 +0200
fix the docs
Diffstat:
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/manpages/taler-mdb-network-check.sh.1.rst b/manpages/taler-mdb-network-check.sh.1.rst
@@ -13,10 +13,11 @@ Synopsis
========
**taler-mdb-network-check.sh**
-[**-c** *FILENAME* | **--config=**\ \ *FILENAME*]
+[**-c** *FILENAME* ]
+[**-f** *FAIL_HELPER* ]
[**-h** | **--help**]
-[*ERRORCODE*]
-
+[**--**]
+[*PROGRAM*]
Description
===========
@@ -29,14 +30,14 @@ Its options are as follows:
**-c** *FILENAME*
Use the configuration and other resources for the command to operate from *FILENAME*.
-**-f** *FILENAME*
+**-f** *FAIL_HELPER*
Overwrites the Taler config's *FAIL_HELPER* value. See taler.conf(5)
**-h**
Print short help on options.
-When the network goes down, it will call *FAIL_HELPER* with one of the following arguments - note that we check in the order these are listed:
+When the network goes down, it will kill *PROGRAM*, then call *FAIL_HELPER* with one of the following error codes (followed by relaunching *PROGRAM* and killing *FAIL_HELPER* once the network is up again) - note that we check in the order these are listed:
**no-ip**
Network Down: Could not reach the DNS Server. (DNS Server is first **nameserver** entry in **/etc/resolv.conf**)
@@ -57,6 +58,13 @@ When the network goes down, it will call *FAIL_HELPER* with one of the following
Backend Auth Failure: Taler credentials are invalid. Check machine configuration.
+The aforementioned *FAIL_HELPER* also gets called if the network isn't up in the first place.
+
+In short, *FAIL_HELPER* will be running whenever then etwork is down, and *PROGRAM* will be running whenever it's up.
+
+The network is checked every **30 seconds**.
+
+
See Also
========
