head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.50; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.08; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.55; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.10.15.03.47.30; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @
DB->set_errfile |
![]() ![]() |
#include <db.h>void DB->set_errfile(DB *db, FILE *errfile);
The DB_ENV->set_errfile and DB->set_errfile functions are used to enhance the mechanism for reporting error messages to the application by setting a C library FILE * to be used for displaying additional Berkeley DB error messages. In some cases, when an error occurs, Berkeley DB will output an additional error message to the specified file reference.
The error message will consist of the prefix string and a colon (":") (if a prefix string was previously specified using DB->set_errpfx or DB_ENV->set_errpfx), an error string, and a trailing <newline> character.
This error logging enhancement does not slow performance or significantly increase application size, and may be run during normal operation as well as during application debugging.
For DB handles opened inside of Berkeley DB environments, calling the DB->set_errfile function affects the entire environment and is equivalent to calling the DB_ENV->set_errfile function.
The DB->set_errfile interface may be used to configure Berkeley DB at any time during the life of the application.
![]() ![]() |
Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 2 a2 2 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 2 a2 2 d45 1 a45 1
For DB handles opened inside of Berkeley DB environments, calling the @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 3 a3 3 a4 1 d33 1 a33 1
The DB_ENV->set_errfile and DB->set_errfile methods are used to d45 5 a49 7
For DB handles opened inside of Berkeley DB environments, calling the DB->set_errfile method affects the entire environment and is equivalent to calling the DB_ENV->set_errfile method.
The DB->set_errfile interface may be called at any time during the life of the application.
The DB_ENV->set_errfile and DB->set_errfile functions are used to d46 7 a52 5
For DB handles opened inside of Berkeley DB environments, calling the DB->set_errfile function affects the entire environment and is equivalent to calling the DB_ENV->set_errfile function.
The DB->set_errfile interface may be used to configure Berkeley DB at any time during the life of the application. d54 1 a54 46 db_create, DB->associate, DB->close, DB->cursor, DB->del, DB->err, DB->errx DB->fd, DB->get, DB->pget, DB->get_byteswapped, DB->get_type, DB->join, DB->key_range, DB->open, DB->put, DB->remove, DB->rename, DB->set_alloc, DB->set_append_recno, DB->set_bt_compare, DB->set_bt_minkey, DB->set_bt_prefix, DB->set_cachesize, DB->set_dup_compare, DB->set_errcall, DB->set_errfile, DB->set_errpfx, DB->set_feedback, DB->set_flags, DB->set_h_ffactor, DB->set_h_hash, DB->set_h_nelem, DB->set_lorder, DB->set_pagesize, DB->set_paniccall, DB->set_q_extentsize, DB->set_re_delim, DB->set_re_len, DB->set_re_pad, DB->set_re_source, DB->stat, DB->sync, DB->truncate, DB->upgrade, and DB->verify. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 3 a3 3 a4 1 d33 1 a33 1
The DB_ENV->set_errfile and DB->set_errfile methods are used to d45 5 a49 7
For DB handles opened inside of Berkeley DB environments, calling the DB->set_errfile method affects the entire environment and is equivalent to calling the DB_ENV->set_errfile method.
The DB->set_errfile interface may be called at any time during the life of the application.