- Fix #1300: Is 'sock-queue-timeout' a linux only feature.

diff --git a/doc/Changelog b/doc/Changelog
index 920f997aa60f4ed69cd9bb85366ab0e3e17be410..fa29c32dda2ffd4e0ceb9903e2ad035b8e777a4a 100644 (file)
--- a/doc/Changelog
+++ b/doc/Changelog
@@ -1,3 +1,6 @@
+3 July 2025: Wouter
+       - Fix #1300: Is 'sock-queue-timeout' a linux only feature.
+
 2 July 2025: Wouter
        - Merge #1299: Fix typos.
        - Generate ltmain.sh and configure again.

diff --git a/doc/unbound.conf.rst b/doc/unbound.conf.rst
index bfc18ba2e581b59ded5ff3df084688720e684faa..2f1f96340b3b788e7b25ee453fa750008d77131b 100644 (file)
--- a/doc/unbound.conf.rst
+++ b/doc/unbound.conf.rst
@@ -910,6 +910,7 @@ These options are part of the **server:** clause.
     This could happen if the host has not been able to service the queries for
     a while, i.e. Unbound is not running, and then is enabled again.
     It uses timestamp socket options.
+    The socket option is available on the Linux platform.
 
     Default: 0 (disabled)