head 1.4; access; symbols RPM_4_2_1:1.1.1.1 RPM_4_2:1.1.1.1 RPM_4_1_1:1.1.1.1 RPM_4_0_5:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.4 date 2008.01.02.09.52.57; author rse; state dead; branches; next 1.3; commitid z4cpSiAhOCXk5PLs; 1.3 date 2003.08.24.12.43.10; author rse; state Exp; branches; next 1.2; 1.2 date 2003.08.24.12.33.45; author rse; state dead; branches; next 1.1; 1.1 date 2002.09.19.20.34.02; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2002.09.19.20.34.02; author rse; state Exp; branches; next ; desc @@ 1.4 log @remove the ancient RPM 4.2.1 source tree copy @ text @
DB_ENV->set_rep_limit |
![]() ![]() |
#include <db.h>int DB_ENV->set_rep_limit(DB_ENV *env, u_int32_t gbytes, u_int32_t bytes);
The DB_ENV->set_rep_limit method imposes a limit on the amount of data that will be transmitted from a site during the course of a single call to DB_ENV->rep_process_message method.
The gbytes and bytes parameters together represent the maximum number of bytes that can be sent during a single call to DB_ENV->rep_process_message method.
The DB_ENV->set_rep_limit method configures a database environment, not only operations performed using the specified DB_ENV handle.
The DB_ENV->set_rep_limit interface may be called at any time during the life of the application.
The DB_ENV->set_rep_limit method returns a non-zero error value on failure and 0 on success.
The DB_ENV->set_rep_limit method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_rep_limit method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
![]() ![]() |
Copyright Sleepycat Software @ 1.3 log @Resolve: RPM 4.1 -> RPM 4.1.1 @ text @@ 1.2 log @Resolve: RPM 4.0.5 -> RPM 4.1 @ text @@ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import: RPM 4.0.5 @ text @@