Allow TTL values when configuring TTLs and time intervals.

Options updated to use ttlvals: max-cache-ttl, max-ncache-ttl,
max-policy-ttl, fstrm-set-reopen-interval, interface-interval, and
min-update-interval.

doc/arm/Bv9ARM-book.xml

@@ -4454,6 +4454,8 @@ badresp:1,adberr:0,findfail:0,valfail:0]
 		    reopen a closed output stream. The minimum is 1 second,
 		    the maximum is 600 seconds (10 minutes), and the default
 		    is 5 seconds.
+		    For convenience, TTL-style time unit suffixes may be
+		    used to specify the value.
 		  </simpara>
 		</listitem>
 	      </itemizedlist>
@@ -8560,8 +8562,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
 		  begin listening for queries on any newly discovered
 		  interfaces (provided they are allowed by the
 		  <command>listen-on</command> configuration), and
-		  will
-		  stop listening on interfaces that have gone away.
+		  will stop listening on interfaces that have gone away.
+		  For convenience, TTL-style time unit suffixes may be
+		  used to specify the value.
 		</para>
 	      </listitem>
 	    </varlistentry>
@@ -8871,8 +8874,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
 		  To reduce network traffic and increase performance,
 		  the server stores negative answers. <command>max-ncache-ttl</command> is
 		  used to set a maximum retention time for these answers in
-		  the server
-		  in seconds. The default
+		  the server in seconds.
+		  For convenience, TTL-style time unit suffixes may be
+		  used to specify the value.  The default
 		  <command>max-ncache-ttl</command> is <literal>10800</literal> seconds (3 hours).
 		  <command>max-ncache-ttl</command> cannot exceed
 		  7 days and will
@@ -8887,6 +8891,8 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
 		<para>
 		  Sets the maximum time for which the server will
 		  cache ordinary (positive) answers in seconds.
+		  For convenience, TTL-style time unit suffixes may be
+		  used to specify the value.
 		  The default is 604800 (one week).
 		  A value of zero may cause all queries to return
 		  SERVFAIL, because of lost caches of intermediate
@@ -10164,6 +10170,8 @@ deny-answer-aliases { "example.net"; };
 	    to a maximum value.
 	    The <command>max-policy-ttl</command> clause changes the
 	    maximum seconds from its default of 5.
+	    For convenience, TTL-style time unit suffixes may be
+	    used to specify the value.
 	  </para>
 
 	  <para>
@@ -10250,6 +10258,8 @@ example.com                 CNAME   rpz-tcp-only.
 	    than <option>min-update-interval</option> seconds after the most
 	    recent update, then the changes will not be carried out until this
 	    interval has elapsed.  The default is <literal>5</literal> seconds.
+	    For convenience, TTL-style time unit suffixes may be
+	    used to specify the value.
 	  </para>
 	</section>
 

doc/arm/notes.xml

@@ -140,6 +140,21 @@
 	  supported by default; previously the limit was 32. [GL #123]
 	</para>
       </listitem>
+      <listitem>
+	<para>
+	  Several configuration options for time periods can now use
+	  TTL value suffixes (for example, <literal>2h</literal> or
+	  <literal>1d</literal>) in addition to an integer number of
+	  seconds. These include:
+	  <command>fstrm-set-reopen-interval</command>;
+	  <command>interface-interval</command>;
+	  <command>max-cache-ttl</command>;
+	  <command>max-ncache-ttl</command>;
+	  <command>max-policy-ttl</command>;
+	  <command>min-update-interval</command>.
+	  [GL #203]
+	</para>
+      </listitem>
     </itemizedlist>
   </section>