On the matter of duplicate keys in DBM files: It has been pointed out to
me that all the DBM libraries have a facility for giving an error code
when attempting to update with an existing key. I had forgotten this. It
turns out to be quite easy to cause dbmbuild to make use of this
facility. Consequently, I have made the following change in the next
release:
5. The exim_dbmbuild utility now warns if it encounters a duplicate key. By
default, only the first of a set of duplicates is used - this is a change from
the previous state, but it does make it compatible with lsearch lookups. There
is an option -lastdup which causes it to use the last instead, which is
compatible with what it did before. There is also an option -nowarn, which
stops it listing duplicate keys to stderr. If any duplicates are encountered,
the return code is 1. For other errors, where it doesn't actually make a new
file, the return code is 2.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
