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.53; 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.56; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.07.58; 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_ENV->set_feedback |
![]() ![]() |
#include <db.h>int DB_ENV->set_feedback(DB_ENV *, void (*db_feedback_fcn)(DB_ENV *, int opcode, int pct));
Some operations performed by the Berkeley DB library can take non-trivial amounts of time. The DB_ENV->set_feedback function can be used by applications to monitor progress within these operations.
When an operation is likely to take a long time, Berkeley DB will call the specified callback function. This function must be declared with three arguments: the first will be a reference to the enclosing environment, the second a flag value, and the third the percent of the operation that has been completed, specified as an integer value between 0 and 100. It is up to the callback function to display this information in an appropriate manner.
The opcode argument may take on any of the following values:
The DB_ENV->set_feedback interface may be used to configure Berkeley DB at any time during the life of the application.
The DB_ENV->set_feedback function returns a non-zero error value on failure and 0 on success.
![]() ![]() |
Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d60 2 d63 1 d66 1 d68 1 a68 1 DB_ENV->set_tas_spins, a69 1 DB_ENV->set_timeout, @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d30 1 a30 1 amounts of time. The DB_ENV->set_feedback method can be used by d43 3 a45 5
The DB_ENV->set_feedback interface may be called at any time during the life of the application.
The DB_ENV->set_feedback method returns a non-zero error value on failure and 0 on success.
The DB_ENV->set_feedback interface may be used to configure Berkeley DB at any time during the life of the application.
The DB_ENV->set_feedback function returns a non-zero error value on failure and 0 on success. d50 1 a50 24 db_env_create, DB_ENV->close, DB_ENV->err, DB_ENV->errx DB_ENV->open, DB_ENV->remove, DB_ENV->set_alloc, DB_ENV->set_cachesize, DB_ENV->set_data_dir, DB_ENV->set_errcall, DB_ENV->set_errfile, DB_ENV->set_errpfx, DB_ENV->set_feedback, DB_ENV->set_flags, DB_ENV->set_paniccall, DB_ENV->set_recovery_init, DB_ENV->set_rpc_server, DB_ENV->set_shm_key, DB_ENV->set_tas_spins, DB_ENV->set_tmp_dir, DB_ENV->set_timeout, DB_ENV->set_verbose, db_strerror and db_version. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d30 1 a30 1 amounts of time. The DB_ENV->set_feedback method can be used by d43 3 a45 5
The DB_ENV->set_feedback interface may be called at any time during the life of the application.
The DB_ENV->set_feedback method returns a non-zero error value on failure and 0 on success.