### Berkeley DB Reference Guide: Programmer Notes |

# Run-time configuration

There are a few interfaces that support run-time configuration of Berkeley DB. First is a group of interfaces that allow applications to intercept Berkeley DB requests for underlying library or system call functionality:

>     db_env_set_func_close
>     db_env_set_func_dirfree
>     db_env_set_func_dirlist
>     db_env_set_func_exists
>     db_env_set_func_free
>     db_env_set_func_fsync
>     db_env_set_func_ioinfo
>     db_env_set_func_malloc
>     db_env_set_func_map
>     db_env_set_func_open
>     db_env_set_func_read
>     db_env_set_func_realloc
>     db_env_set_func_seek
>     db_env_set_func_sleep
>     db_env_set_func_unlink
>     db_env_set_func_unmap
>     db_env_set_func_write
>     db_env_set_func_yield

These interfaces are only available from the Berkeley DB C language API.

In addition, there are a few interfaces that allow applications to re-configure, on an application-wide basis, Berkeley DB behaviors.

>     DBENV->set_mutexlocks
>     db_env_set_pageyield
>     db_env_set_panicstate
>     db_env_set_region_init
>     db_env_set_tas_spins

These interfaces are available from all of the Berkeley DB programmatic APIs.

A not-uncommon problem for applications is the new API in Solaris 2.6 for manipulating large files. As this API was not part of Solaris 2.5, it is difficult to create a single binary that takes advantage of the large file functionality in Solaris 2.6 but which still runs on Solaris 2.5. Example code that supports this is included in the Berkeley DB distribution.

Copyright Sleepycat Software