From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] unbound: Update to 1.23.0
Date: Wed, 7 May 2025 17:32:53 +0200 [thread overview]
Message-ID: <a052bc74-8c93-4bdf-88d1-632a6e896236@ipfire.org> (raw)
In-Reply-To: <84FE7A44-CB93-4B9F-92D4-10E717DADD65@ipfire.org>
On 07.05.2025 11:54, Michael Tremer wrote:
> Hello Matthias,
Hi,
> Thanks for the patch. I added another patch to use the new fast reload feature:
>
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=bc3c914b12689a8f245b2332bc6055bcc3f3dc89
>
> Hopefully reloading Unbound will be less disruptive to the network then.
But doesn't that mean that unbound has to be compiled with
"--with-pthreads"!?
=>
https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound-control.html#
says:
"fast_reload [+dpv]
Reload the server, but keep downtime to a minimum, so that user
queries keep seeing service. This needs the code compiled with threads..."
Or is that option active by default? Do we need "num-threads" in the
config? I'm just not 100% sure...
Best
Matthias
> -Michael
>
>> On 5 May 2025, at 15:12, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>
>> For details see:
>> https://nlnetlabs.nl/projects/unbound/download/#unbound-1-23-0
>>
>> Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
>> ---
>> config/rootfiles/common/unbound | 2 +-
>> lfs/unbound | 6 +++---
>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/config/rootfiles/common/unbound b/config/rootfiles/common/unbound
>> index 57390d6d9..8913c376f 100644
>> --- a/config/rootfiles/common/unbound
>> +++ b/config/rootfiles/common/unbound
>> @@ -11,7 +11,7 @@ etc/unbound/unbound.conf
>> #usr/lib/libunbound.la
>> #usr/lib/libunbound.so
>> usr/lib/libunbound.so.8
>> -usr/lib/libunbound.so.8.1.30
>> +usr/lib/libunbound.so.8.1.31
>> #usr/lib/pkgconfig/libunbound.pc
>> usr/sbin/unbound
>> usr/sbin/unbound-anchor
>> diff --git a/lfs/unbound b/lfs/unbound
>> index 537ccff7e..abcb4e104 100644
>> --- a/lfs/unbound
>> +++ b/lfs/unbound
>> @@ -1,7 +1,7 @@
>> ###############################################################################
>> # #
>> # IPFire.org - A linux based firewall #
>> -# Copyright (C) 2007-2024 IPFire Team <info@ipfire.org> #
>> +# Copyright (C) 2007-2025 IPFire Team <info@ipfire.org> #
>> # #
>> # This program is free software: you can redistribute it and/or modify #
>> # it under the terms of the GNU General Public License as published by #
>> @@ -24,7 +24,7 @@
>>
>> include Config
>>
>> -VER = 1.22.0
>> +VER = 1.23.0
>>
>> THISAPP = unbound-$(VER)
>> DL_FILE = $(THISAPP).tar.gz
>> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>>
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>
>> -$(DL_FILE)_BLAKE2 = 28cf5c6c5e29d4026beb33e8a17b012d1185a3a100fafd3e2717233f47c7b0ad2bf7b7fc2d5ad8c15b6fef496ed9d9c95d116535c3c34c945b27c2a42fa197ff
>> +$(DL_FILE)_BLAKE2 = 160bb2bee5450313a68ac81b73fd4bb21b14f8d25172d314644a34309dc75f28802126533f3ac1cb8d48599af8cb7caca83b866c9193286396f81c5fabc29651
>>
>> install : $(TARGET)
>>
>> --
>> 2.43.0
>>
>>
>
>
next prev parent reply other threads:[~2025-05-07 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 14:12 Matthias Fischer
2025-05-07 9:54 ` Michael Tremer
2025-05-07 15:32 ` Matthias Fischer [this message]
2025-05-07 15:40 ` Michael Tremer
2025-05-08 9:34 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a052bc74-8c93-4bdf-88d1-632a6e896236@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox