and should now format cleanly using most versions of
nroff, and HTML versions of the man pages hvae been
added. Both are generated from DocBook source.
so that they don't keep appearing and disappearing depending
on whether "make man" or "update_copyright" was run last.
Also, moved HTML_COPYRIGHT and MAN_COPYRIGHT to a new
directory "docutil" which is actually shipped with the
distribution, unlike the "util" directory.
the optional debug level in a "severity debug"
clause of a logging channel to be omitted.
This is now allowed and treated as "severity
debug 1;" like it did in BIND 8.2.4, not as
"severity debug 0;" like it did in BIND 9.1.
[RT #1367]
is now on by default for IRIX and HPUX, do that in a separate
change log entry 864, since this change was visible to users in an
(alpha) release. Also, added --- 9.2.0a1 released --- tag to mainline
CHANGES file since the version released, although technically done from
a branch, was in practice identical to what was on the mainline at the time.
was starting up, the server could access a domain
name that had already been freed when logging a
message saying that the transfer was starting.
[RT #1383]
is a persistent overlimit condition.
858. [func] isc_mem_setwater() no longer requires that when the
callback function is non-NULL then its hi_water
argument must be greater than its lo_water argument
(they can now be equal) or that they be non-zero.
857. [cleanup] Use ISC_MAGIC() to define all magic numbers for
structs, for our friends in EBCDIC-land.
wait at least six seconds between each pass of the tree. This keeps
the CPU from being bogged down in a persistent overlimit condition, and
because it uses timers also lets the cache cleaner know right away when
the server is being shut down, so it can stop trying to clean.
Also fixed an unlocked access to cache->live_tasks in dns_cache_detach().
Also fixed a problem with repeated calls to dns_cache_setcachesize() setting
the database as not overmem, even though it might have still been in
the process of cleaning from a previous limit. Just set the new
isc_mem_setwater() limits instead and let the mem.c call water() if cleaning
needs to be either started or stopped because of the new limits.
Minor code cleanups.
is not null then hi_water must exceed lo_water and both must be > 0.
Now requires hi_water >= lo_water, and they can both be 0. Not allowing
them to be equal was just an unnecessary restriction, and letting them be 0
is useful for the case where the context has had non-zero values set, went
over hi_water and called the callback, and then wanted to remove limits
(perhaps because of a reconfiguration). This allows the callback to
be signaled as ISC_MEM_LOWATER on the next isc_mem_put(), which the caller
might need to terminate any outstanding action that was triggered by
the hi_water.
