From: Tinderbox User Date: Wed, 8 Feb 2017 01:08:12 +0000 (+0000) Subject: regen v9_11 X-Git-Tag: v9.11.1rc2~21 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4d4242b7448f30965a718e7db31a3ae2bd2e165f;p=thirdparty%2Fbind9.git regen v9_11 --- diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html index 5d6831f5ede..f3fb8b6f4ec 100644 --- a/doc/arm/Bv9ARM.ch09.html +++ b/doc/arm/Bv9ARM.ch09.html @@ -252,15 +252,15 @@
  • - Named could deadlock there were multiple changes to - NSEC/NSEC3 parameters for a zone being processed at the - same time. [RT #42770] + named could deadlock if multiple changes + to NSEC/NSEC3 parameters for the same zone were being processed + at the same time. [RT #42770]

  • - Named could trigger a assertion when sending notify - messages. [RT #44019] + named could trigger an assertion when + sending NOTIFY messages. [RT #44019]

  • diff --git a/doc/arm/notes.html b/doc/arm/notes.html index 111657d6d58..abb2e99f8f5 100644 --- a/doc/arm/notes.html +++ b/doc/arm/notes.html @@ -213,15 +213,15 @@
  • - Named could deadlock there were multiple changes to - NSEC/NSEC3 parameters for a zone being processed at the - same time. [RT #42770] + named could deadlock if multiple changes + to NSEC/NSEC3 parameters for the same zone were being processed + at the same time. [RT #42770]

  • - Named could trigger a assertion when sending notify - messages. [RT #44019] + named could trigger an assertion when + sending NOTIFY messages. [RT #44019]