commit 520dad0b261732c2979de01bf0534ac79e8161e0 parent ea9af7ad5fa81477c655d1e0a7a890a5cf224b6e Author: Christian Grothoff <christian@grothoff.org> Date: Sat, 19 Feb 2022 21:21:42 +0100 -document what happens when fakebank exceeds RAM pool limit Diffstat:
| M | manpages/taler-fakebank-run.1.rst | | | 2 | ++ |
| M | manpages/taler.conf.5.rst | | | 12 | ++++++++++++ |
2 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/manpages/taler-fakebank-run.1.rst b/manpages/taler-fakebank-run.1.rst @@ -24,6 +24,8 @@ Description **taler-fakebank-run** is a command-line tool to run a Taler "bank" API (HTTP REST service). The program is useful to provide the bank functionality for benchmarking or testing when LibEuFin is unavailable or otherwise unsuitable. +It should be noted that the fakebank will keep a configured number of transactions in memory. If the number of transactions exceeds the configured memory limit, the fakebank will simply discard and overwrite the old entries. At that point, any requests involving such overwritten transactions will fail. Users of the fakebank are responsible for ensuring that the transaction history kept in memory is long enough for the purpose the bank is used for. The default limit is 128k entries. + Its options are as follows: **-C** \| **--connection-close** diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst @@ -505,6 +505,18 @@ CONFIG "taler" database. Testcases use “talercheck”. +Bank Options +------------ + +The following options must be in section "[bank]" for the taler-fakebank-run(1) command. They are not used by the exchange or LibEuFin! + +HTTP_PORT + On which TCP port should the (fake)bank offer its REST API. +RAM_LIMIT + This gives the number of transactions to keep in memory. Older transactions will be overwritten and history requests for overwritten transactions will fail. + + + SEE ALSO ========