#include <db.h>

int
DB_ENV->rep_set_config(DB_ENV *env, u_int32_t which, int onoff);

int
DB_ENV->rep_get_config(DB_ENV *dbenv, u_int32_t which, int *onoffp);

The DB_ENV->rep_set_config method method configures the Berkeley DB replication subsystem.

The database environment's replication subsystem may also be configured using the environment's DB_CONFIG file. The syntax of the entry in that file is a single line with the string "rep_set_config", one or more whitespace characters, and the method which parameter as a string; for example, "rep_set_config DB_REP_CONF_NOWAIT". Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

The DB_ENV->rep_set_config method configures a database environment, not only operations performed using the specified DB_ENV handle.

The DB_ENV->rep_set_config method may be called at any time during the life of the application.

The DB_ENV->rep_set_config method returns a non-zero error value on failure and 0 on success.

• If the onoff parameter is zero, the configuration flag is turned off. Otherwise, it is turned on.

• The which parameter must be set to one of the following values:
  DB_REP_CONF_BULK
  • The replication master sends groups of records to the clients in a single network transfer (defaults to off).
  DB_REP_CONF_DELAYCLIENT
  • The client should delay synchronizing to a newly declared master (defaults to off). Clients configured in this way will remain unsynchronized until the application calls the DB_ENV->rep_sync method.
  DB_REP_CONF_LEASE
  • Master leases will be used for this site (defaults to off).

    Configuring this option may result in DB_REP_LEASE_EXPIRED error returns from the DB->get and DBcursor->get methods when attempting to read entries from a database after the site's master lease has expired.

    The DB_ENV->rep_set_config method may not be called after the DB_ENV->repmgr_start or DB_ENV->rep_start methods are called.

    Once this option is turned on, it may never be turned off.
  DB_REP_CONF_NOAUTOINIT
  • The replication master will not automatically re-initialize outdated clients (defaults to off).
  DB_REP_CONF_NOWAIT
  • Berkeley DB method calls that would normally block while clients are in recovery will return errors immediately (defaults to off).
  DB_REPMGR_CONF_2SITE_STRICT
  • Replication Manager observes the strict "majority" rule in managing elections, even in a group with only 2 sites. This means the client in a 2-site group will be unable to take over as master if the original master fails or becomes disconnected. (See the Elections section in the Berkeley DB Reference Guide for more information.) Both sites in the replication group should have the same value for this parameter.
  
  

The DB_ENV->rep_set_config method may fail and return one of the following non-zero errors:

• An invalid flag value or parameter was specified.

The DB_ENV->rep_get_config method returns whether the specified which parameter is currently set or not.

The DB_ENV->rep_get_config method may be called at any time during the life of the application.

The DB_ENV->rep_get_config method returns a non-zero error value on failure and 0 on success.

• The which parameter is the message value for which configuration is being checked.

• The onoffp parameter references memory into which the configuration of the specified which parameter is copied.