From 588eab6792581d9d9d23de3f3fa6290aebdb1cad Mon Sep 17 00:00:00 2001 From: dzwdz Date: Tue, 16 Sep 2025 04:57:37 +0200 Subject: [PATCH] clean up MaxHSDirCacheBytes docs slop? in my tor(1)? more likely than you think I don't think any other entries use "Default" lke this, and the repetition seems pointless. The historical context was broken off to keep the "main" part short and tidy. --- doc/man/tor.1.txt | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt index ebd1f2adb9..5b3006b4e5 100644 --- a/doc/man/tor.1.txt +++ b/doc/man/tor.1.txt @@ -2432,11 +2432,12 @@ is non-zero): [[MaxHSDirCacheBytes]] **MaxHSDirCacheBytes** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**:: This option configures a threshold of Hidden Service Directory memory consumption above which your Tor relay will begin to prune the least-frequently - accessed hidden service descriptors from the relay's HSDir cache. This pruning used - to be done as part of MaxMemInQueues, but it has been decoupled to allow more - fine-grained control of descriptor cache size under DDoS conditions. This - option defaults to 20% of the MaxMemInQueues size, which itself defaults to - an automatically determined value based on system memory. (Default: 20% MaxMemInQueues) + accessed hidden service descriptors from the relay's HSDir cache. + If set to 0, this will default to 20% of MaxMemInQueues. (Default: 0) + + + + This pruning used to be done as part of MaxMemInQueues, but it has been + decoupled to allow more fine-grained control of descriptor cache size under + DDoS conditions. [[MaxMemInQueues]] **MaxMemInQueues** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**:: This option configures a threshold above which Tor will assume that it -- 2.47.3