commit 446bb85a95622533d354ac515dc906f5eb76048c parent a4ea3513a56a3fe92e988349c50219b2d6798a67 Author: Florian Dold <florian@dold.me> Date: Sat, 7 Aug 2021 23:04:22 +0200 questions / slashes Diffstat:
| M | libeufin/nexus-tutorial.rst | | | 4 | ++-- |
| M | taler-exchange-setup-guide.rst | | | 5 | +++++ |
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/libeufin/nexus-tutorial.rst b/libeufin/nexus-tutorial.rst @@ -463,8 +463,8 @@ once at 11pm every day : .. code-block:: console $ libeufin-cli accounts task-schedule myacct \ - --task-type="submit" - --task-name='submit-payments-hourly' + --task-type="submit" \ + --task-name='submit-payments-hourly' \ --task-cronspec='0 0 *' $ libeufin-cli accounts task-schedule myacct \ diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst @@ -978,3 +978,8 @@ FIXMEs running. Systemd by default doesn't show this nicely. Maybe suggest running "systemd list-dependencies taler-exchange.target"? * When multiple TWGs are configured, which one will be used by the taler-exchange-transfer? CG: ALL! + + * FD: Sure, for incoming transactions. But how does taler-exchange-transfer decide which TWG to use for an outgoing transaction? + +* What happens when the TWG doesn't like one particular outgoing transaction? + How to recover from that as a sysadmin when it happens in practice?