commit 11f992c7a5bcc74c9c638e27826ce94250dc1671
parent 9f852a613424170c92fbec9dfd80f41aa70f8659
Author: Christian Grothoff <christian@grothoff.org>
Date: Tue, 3 Jun 2025 14:43:38 +0200
update docs for #9053: new taler-exchange-sanctioncheck command-line options and config file options
Diffstat:
2 files changed, 26 insertions(+), 1 deletion(-)
diff --git a/manpages/taler-exchange-sanctionscheck.1.rst b/manpages/taler-exchange-sanctionscheck.1.rst
@@ -16,8 +16,11 @@ Synopsis
[**-h** | **--help**]
[**-L** *LOGLEVEL* | **--loglevel=**\ \ *LOGLEVEL*]
[**-l** *FILENAME* | **--logfile=**\ \ *FILENAME*]
+[**-n** | **--norun**]
+[**-r** | **--reset**]
+[**-t** | **--testmode**]
[**-v** | **--version**] --
-SANCTIONCHECKER [SANCTIONCHECKER_ARGUMENTS
+SANCTIONCHECKER [SANCTIONCHECKER_ARGUMENTS]
Description
===========
@@ -44,6 +47,15 @@ Its options are as follows:
**-l** *FILENAME* \| **--logfile=**\ \ *FILENAME*
Send logging output to *FILENAME*.
+**-n** \| **--norun**
+ Skips the actual processing of KYC records. Useful only to check the setup or to reset processing to the start in combination with **-r**.
+
+**-r** \| **--reset**
+ Resets the sanction list processing progress. Useful when a new sanction list is imported to go again over all historic records and check them again.
+
+**-t** \| **--test**
+ Run in test mode. Exits once all records that existed on start have been processed and skips the incremental phase. Sanction list progress is still persisted. Useful in test cases or interactively when waiting for completion.
+
**-v** \| **--version**
Print version information.
diff --git a/manpages/taler-exchange.conf.5.rst b/manpages/taler-exchange.conf.5.rst
@@ -669,6 +669,19 @@ UNIXPATH
.. include:: frags/exchange-account.rst
.. include:: frags/exchange-coin.rst
+EXCHANGE SANCTIONSCHECK OPTIONS
+-------------------------------
+
+The following options must be in the section "[exchange-sanctionscheck]".
+
+MIN_ROW_FILENAME
+ Name of the file where taler-exchange-sanctionscheck will store the
+ last row process during sanction list evaluation. Not in the database
+ as we frequently need to reset it when we get a new list, so no
+ transactionality is needed or even desirable. There should be no
+ need to change the default.
+
+
SEE ALSO
========