From: madblobfish <12998362+madblobfish@users.noreply.github.com>
Date: Sun, 14 Dec 2025 19:53:25 +0000 (+0100)
Subject: Add reference to journal behaviour paragraph in operation.rst
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f10adc91667c7c493f3729fd2a1202c3de97c1a4;p=thirdparty%2Fknot-dns.git

Add reference to journal behaviour paragraph in operation.rst

Adds a reference to the journal-max-usage zone configuration parameter
in a paragraph in the operation.rst file which mentions per-zone limits.
Also reformatted lines of said paragraph due to reaching 80 characters.
---

diff --git a/doc/operation.rst b/doc/operation.rst
index 47dd1c4e83..15f51f4016 100644
--- a/doc/operation.rst
+++ b/doc/operation.rst
@@ -357,11 +357,12 @@ If the journal is used to store both zone history and contents, a special change
 is present with zone contents. When the journal gets full, the changes are merged into this
 special changeset.
 
-There is also a :ref:`safety hard limit <database_journal-db-max-size>` for overall
-journal database size, but it's strongly recommended to set the per-zone limits in
-a way to prevent hitting this one. For LMDB, it's hard to recover from the
-database-full state. For wiping one zone's journal, see *knotc zone-purge +journal*
-command.
+There is also a :ref:`safety hard limit <database_journal-db-max-size>`
+for overall journal database size, but it's strongly recommended to
+set :ref:`the per-zone limits <zone_journal-max-usage>` in a way to
+prevent hitting this one.
+For LMDB, it's hard to recover from the database-full state.
+For wiping one zone's journal, see *knotc zone-purge +journal* command.
 
 .. [#fn-hc] This constant is hardcoded.