Changeset 1723

Timestamp:

09/23/10 22:42:25 (3 years ago)

Author:

ahu

Message:

3.3 docs

Files:

• trunk/pdns/pdns/docs/pdns.sgml (modified) (7 diffs)

trunk/pdns/pdns/docs/pdns.sgml

@@ -93 +93 @@
         Beyond PowerDNS 2.9.20, the Authoritative Server and Recursor are released separately.
       </para>
-      <sect2 id="changelog-recursor-3-3"><title>Recursor version 3.3 (RC1!) </title>
+      <sect2 id="changelog-recursor-3-3"><title>Recursor version 3.3 </title>
         <para>
           <warning>
             <para>
-              Release Candidate 1 released on the 11th of September 2010.
+              Released on the 22nd of September 2010.
             </para>
           </warning>
         </para>
         <para>
-          Version 3.3 fixes a number of small but persistent issues, rounds off our IPv6 support and adds
+          Version 3.3 fixes a number of small but persistent issues, rounds off our IPv6 %link-level support and adds
           an important feature for many users of the Lua scripts. 
         </para>
@@ -108 +108 @@
           In addition, scalability on Solaris 10 is improved.
         </para>
+        
         <para>
           Bug fixes:
@@ -152 +153 @@
           <listitem><para>
             The priming of the root now uses more IPv6 addresses. Change in c1550, closes t287. Also, the IPv6 address of I.ROOT-SERVERS.NET was added in c1650.
+          </para></listitem>
+          <listitem><para>
+            The <function>rec_control dump-cache</function> command now also dumps the 'negative query' cache. Code in c1713.
           </para></listitem>
           <listitem><para>
@@ -195 +199 @@
           </para></listitem>
            <listitem><para>
-            Cache cleaning code was cleaned up, unified and expanded to cover the 'negative cache', which used to be cleaned rather bluntly. Code in c1702, spotted by Darren Gamble and Christian Kovacic.
+            Cache cleaning code was cleaned up, unified and expanded to cover the 'negative cache', which used to be cleaned rather bluntly. Code in c1702, further tweaks in c1712, 
+            spotted by Darren Gamble, Imre Gergely and Christian Kovacic.
            </para></listitem>
         </itemizedlist>
+        </para>
+        <para>
+          Changes between RC1, RC2 and RC3.
+          <itemizedlist>
+            <listitem><para>
+              RC2: Fixed linking on RHEL5/CENTOS5, which both ship with a gcc compiler that claims to support atomic operations, but doesn't. Code in c1714. Spotted by 'Bas' and Imre Gergely. 
+            </para></listitem>
+            <listitem><para>
+              RC2: Negative query cache was configured to grow too large, and was not cleaned efficiently. Code in c1712, spotted by Imre Gergely.
+            </para></listitem>
+            <listitem><para>
+              RC3: Root failed to be renewed automatically, relied on fallback to make this happen. Code in c1716, spotted by Detlef Peeters.
+            </para></listitem>
+          </itemizedlist>
         </para>
       </sect2>
@@ -9258 +9277 @@
             <listitem>
               <para>
-                Maximum number of DNS cache entries. 1 million will generally suffice for most installations.
+                Maximum number of DNS cache entries. 1 million per thread will generally suffice for most installations.
               </para>
             </listitem>
@@ -9267 +9286 @@
             <listitem>
               <para>
-                Maximum number of Packet Cache entries. 1 million will generally suffice for most installations. Available since 3.2.
+                Maximum number of Packet Cache entries. 1 million per thread will generally suffice for most installations. Available since 3.2. 
               </para>
             </listitem>
@@ -9597 +9616 @@
           <listitem>
             <para>
-              Limit the size of the caches to a sensible value. Cache hit rate does not improve meaningfully beyond 4 million <command>max-cache-entries</command>,
+              Limit the size of the caches to a sensible value. Cache hit rate does not improve meaningfully beyond 4 million <command>max-cache-entries</command> per thread,
               reducing the memory footprint reduces CPU cache misses. See below for more information about the various caches.
             </para>