From: Michał Kępień Date: Wed, 11 Mar 2020 08:06:40 +0000 (+0100) Subject: Move pthread rwlocks release note to a section X-Git-Tag: v9.17.1~58^2~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f8a8eaba8b58f7c6dc33a564012055bb9ee00afd;p=thirdparty%2Fbind9.git Move pthread rwlocks release note to a section --- diff --git a/doc/arm/notes-9.17.0.xml b/doc/arm/notes-9.17.0.xml index a2ea9c73b21..4844ee18001 100644 --- a/doc/arm/notes-9.17.0.xml +++ b/doc/arm/notes-9.17.0.xml @@ -10,31 +10,33 @@ -->
Notes for BIND 9.17.0 - - System-provided pthread rwlocks implementation is used by default instead of - built-in ISC implementation of rwlocks. Please be aware that unpatched glibc - version from 2.26 had a bug - that could cause BIND 9 to deadlock. The fix has been released as part of - glibc release 2.30, and various Linux distributions have patched their glibc - version with a notable exception of Ubuntu 18.04 (Bionic) which is work in - progress. If you are running on affected system (e.g. Ubuntu 18.04) you need - to compile BIND 9 with --disable-pthread-rwlock until Canonical releases - fixed - version. -
Feature Changes - The rndc nta -dump and - rndc secroots commands now both include - validate-except entries when listing negative - trust anchors. These are indicated by the keyword - permanent in place of the expiry - date. [GL #1532] + System-provided pthread rwlocks implementation is used by default instead of + built-in ISC implementation of rwlocks. Please be aware that unpatched glibc + version from 2.26 had a bug + that could cause BIND 9 to deadlock. The fix has been released as part of + glibc release 2.30, and various Linux distributions have patched their glibc + version with a notable exception of Ubuntu 18.04 (Bionic) which is work in + progress. If you are running on affected system (e.g. Ubuntu 18.04) you need + to compile BIND 9 with --disable-pthread-rwlock until Canonical releases + fixed + version. + + + + + The rndc nta -dump and + rndc secroots commands now both include + validate-except entries when listing negative + trust anchors. These are indicated by the keyword + permanent in place of the expiry + date. [GL #1532] @@ -44,8 +46,8 @@ - Fixed re-signing issues with inline zones which resulted in - records being re-signed late or not at all. + Fixed re-signing issues with inline zones which resulted in + records being re-signed late or not at all. @@ -54,21 +56,21 @@
New Features - - When a secondary server receives a large incremental zone - transfer (IXFR), it can have a negative impact on query - performance while the incremental changes are applied to - the zone. To address this, named can now - limit the size of IXFR responses it sends in response to zone - transfer requests. If an IXFR response would be larger than an - AXFR of the entire zone, it will send an AXFR resonse instead. - - - This behavior is controlled by the max-ixfr-ratio - option - a percentage value representing the ratio of IXFR size - to the size of a full zone transfer. This value cannot exceed - 100%, which is also the default. [GL #1515] - + + When a secondary server receives a large incremental zone + transfer (IXFR), it can have a negative impact on query + performance while the incremental changes are applied to + the zone. To address this, named can now + limit the size of IXFR responses it sends in response to zone + transfer requests. If an IXFR response would be larger than an + AXFR of the entire zone, it will send an AXFR resonse instead. + + + This behavior is controlled by the max-ixfr-ratio + option - a percentage value representing the ratio of IXFR size + to the size of a full zone transfer. This value cannot exceed + 100%, which is also the default. [GL #1515] +