summaryrefslogtreecommitdiff
path: root/taler-exchange-setup-guide.rst
diff options
context:
space:
mode:
authorFlorian Dold <florian@dold.me>2021-08-07 23:04:22 +0200
committerFlorian Dold <florian@dold.me>2021-08-07 23:04:22 +0200
commit446bb85a95622533d354ac515dc906f5eb76048c (patch)
tree43a3632031921e7c2ebe73439caa16c290ec14a5 /taler-exchange-setup-guide.rst
parenta4ea3513a56a3fe92e988349c50219b2d6798a67 (diff)
downloaddocs-446bb85a95622533d354ac515dc906f5eb76048c.tar.gz
docs-446bb85a95622533d354ac515dc906f5eb76048c.tar.bz2
docs-446bb85a95622533d354ac515dc906f5eb76048c.zip
questions / slashes
Diffstat (limited to 'taler-exchange-setup-guide.rst')
-rw-r--r--taler-exchange-setup-guide.rst5
1 files changed, 5 insertions, 0 deletions
diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst
index 375f464c..82b698e5 100644
--- 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?