> As expected. Notice that this message is informational, not a warning
> or an error:
>
> /*
> * With some Berkeley DB implementations, close fails with a bogus ENOENT
> * error, while it reports no errors with put+sync, no errors with
> * del+sync, and no errors with the sync operation just before this
> * comment. This happens in programs that never fork and that never share
> * the database with other processes. The bogus close error has been
> * reported for programs that use the first/next iterator. Instead of
> * making Postfix look bad because it reports errors that other programs
> * ignore, I'm going to report the bogus error as a non-error.
> */
> if (DICT_DB_CLOSE(dict_db->db) < 0)
> msg_info("close database %s: %m", dict_db->dict.name);
>
> Not reporting the anomaly at all may mask real problems in the future.
Hm, so isn't that a bug in BerkeleyDB then - and should be reported?
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | http://www.charite.de
