summaryrefslogtreecommitdiff
path: root/taler-auditor-manual.rst
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2020-12-12 01:13:40 -0500
committerThien-Thi Nguyen <ttn@gnuvola.org>2020-12-12 01:13:40 -0500
commitbcd8520cabc3447559707b7949c543891a14284a (patch)
treec92aacc66b8770a8613dbd075b1add51da472d02 /taler-auditor-manual.rst
parent683d364d283071f9b3524b82aca7f9bf3d67402c (diff)
downloaddocs-bcd8520cabc3447559707b7949c543891a14284a.tar.gz
docs-bcd8520cabc3447559707b7949c543891a14284a.tar.bz2
docs-bcd8520cabc3447559707b7949c543891a14284a.zip
split big para into two
Diffstat (limited to 'taler-auditor-manual.rst')
-rw-r--r--taler-auditor-manual.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index ac42750..76eef84 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -604,7 +604,9 @@ database, the suggestion is to replace the corrupted (and likely very large)
amounts with zero (Note: this does not apply to the value of denominations or
fees, here it is crucial that the correct amounts are restored). While an
amount of zero would be incorrect, the auditing logic should be able to do its
-calculations with zero instead. After patching the database, the audit can
+calculations with zero instead.
+
+After patching the database, the audit can
be restarted. A full reset is not required, as the audit transaction is aborted
when the auditor exits with code *42*. After restarting, the resulting audit
report is likely to indicates errors relating to the corrupted fields (such as