From 444c839474dcb17350bf5dc324392ead4f92a4e1 Mon Sep 17 00:00:00 2001 From: "W.C.A. Wijngaards" Date: Thu, 3 Jul 2025 14:10:46 +0200 Subject: [PATCH] - Fix #1300: Is 'sock-queue-timeout' a linux only feature. --- doc/Changelog | 3 +++ doc/unbound.conf.rst | 1 + 2 files changed, 4 insertions(+) diff --git a/doc/Changelog b/doc/Changelog index 920f997aa..fa29c32dd 100644 --- 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 bfc18ba2e..2f1f96340 100644 --- 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)