upstream/unbound
1
0
Fork 0
mirror of https://github.com/NLnetLabs/unbound.git synced 2026-01-01 20:39:38 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

- More explicit text about memory usage during fast_reload.

Browse source
This commit is contained in:
Yorgos Thessalonikefs 2025-04-07 16:56:38 +02:00
parent db6505eb8b
commit e94e140f49
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/unbound-control.8.in
View file

@ -67,7 +67,16 @@ is loaded in a thread, and prepared, then it briefly pauses the existing
server and updates config options. The intent is that the pause does not
impact the service of user queries. The cache is kept. Also user queries
worked on are kept and continue, but with the new config options.
.IP
This command is experimental at this time.
.IP
The amount of temporal memory needed during a fast_reload is twice the
amount needed for configuration.
This is because Unbound temporarily needs to store both current configuration
values and new ones while trying to fast_reload.
Zones loaded from disk (authority zones and RPZ zones) are included in such
memory needs.
.IP
Not all options are changed, but it changes like forwards, stubs and
local zones. Also access-control and interface-action and similar options,
also tcp-connection-limits, views. It can reload some define-tag changes.