1<?xml version="1.0" encoding="UTF-8" standalone="no"?> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3<html xmlns="http://www.w3.org/1999/xhtml"> 4 <head> 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 6 <title>Run-time configuration</title> 7 <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> 8 <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> 9 <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" /> 10 <link rel="up" href="program.html" title="Chapter 14. Programmer Notes" /> 11 <link rel="prev" href="program_compatible.html" title="Compatibility with historic UNIX interfaces" /> 12 <link rel="next" href="program_faq.html" title="Programmer notes FAQ" /> 13 </head> 14 <body> 15 <div class="navheader"> 16 <table width="100%" summary="Navigation header"> 17 <tr> 18 <th colspan="3" align="center">Run-time configuration</th> 19 </tr> 20 <tr> 21 <td width="20%" align="left"><a accesskey="p" href="program_compatible.html">Prev</a> </td> 22 <th width="60%" align="center">Chapter 14. 23 Programmer Notes 24 </th> 25 <td width="20%" align="right"> <a accesskey="n" href="program_faq.html">Next</a></td> 26 </tr> 27 </table> 28 <hr /> 29 </div> 30 <div class="sect1" lang="en" xml:lang="en"> 31 <div class="titlepage"> 32 <div> 33 <div> 34 <h2 class="title" style="clear: both"><a id="program_runtime"></a>Run-time configuration</h2> 35 </div> 36 </div> 37 </div> 38 <p>It is possible for applications to configure Berkeley DB at run-time to 39redirect Berkeley DB library and system calls to alternate interfaces. For 40example, an application might want Berkeley DB to call debugging memory 41allocation routines rather than the standard C library interfaces. The 42following interfaces support this functionality:</p> 43 <div class="itemizedlist"> 44 <ul type="disc"> 45 <li> 46 <p> 47 <a href="../api_reference/C/db_env_set_func_close.html" class="olink">db_env_set_func_close</a> 48 </p> 49 </li> 50 <li> 51 <p> 52 <a href="../api_reference/C/db_env_set_func_dirfree.html" class="olink">db_env_set_func_dirfree</a> 53 </p> 54 </li> 55 <li> 56 <p> 57 <a href="../api_reference/C/db_env_set_func_dirlist.html" class="olink">db_env_set_func_dirlist</a> 58 </p> 59 </li> 60 <li> 61 <p> 62 <a href="../api_reference/C/db_env_set_func_exists.html" class="olink">db_env_set_func_exists</a> 63 </p> 64 </li> 65 <li> 66 <p> 67 <a href="../api_reference/C/db_env_set_func_file_map.html" class="olink">db_env_set_func_file_map</a> 68 </p> 69 </li> 70 <li> 71 <p> 72 <a href="../api_reference/C/db_env_set_func_free.html" class="olink">db_env_set_func_free</a> 73 </p> 74 </li> 75 <li> 76 <p> 77 <a href="../api_reference/C/db_env_set_func_fsync.html" class="olink">db_env_set_func_fsync</a> 78 </p> 79 </li> 80 <li> 81 <p> 82 <a href="../api_reference/C/db_env_set_func_ftruncate.html" class="olink">db_env_set_func_ftruncate</a> 83 </p> 84 </li> 85 <li> 86 <p> 87 <a href="../api_reference/C/db_env_set_func_ioinfo.html" class="olink">db_env_set_func_ioinfo</a> 88 </p> 89 </li> 90 <li> 91 <p> 92 <a href="../api_reference/C/db_env_set_func_malloc.html" class="olink">db_env_set_func_malloc</a> 93 </p> 94 </li> 95 <li> 96 <p> 97 <a href="../api_reference/C/db_env_set_func_open.html" class="olink">db_env_set_func_open</a> 98 </p> 99 </li> 100 <li> 101 <p> 102 <a href="../api_reference/C/db_env_set_func_pread.html" class="olink">db_env_set_func_pread</a> 103 </p> 104 </li> 105 <li> 106 <p> 107 <a href="../api_reference/C/db_env_set_func_pwrite.html" class="olink">db_env_set_func_pwrite</a> 108 </p> 109 </li> 110 <li> 111 <p> 112 <a href="../api_reference/C/db_env_set_func_read.html" class="olink">db_env_set_func_read</a> 113 </p> 114 </li> 115 <li> 116 <p> 117 <a href="../api_reference/C/db_env_set_func_realloc.html" class="olink">db_env_set_func_realloc</a> 118 </p> 119 </li> 120 <li> 121 <p> 122 <a href="../api_reference/C/db_env_set_func_region_map.html" class="olink">db_env_set_func_region_map</a> 123 </p> 124 </li> 125 <li> 126 <p> 127 <a href="../api_reference/C/db_env_set_func_rename.html" class="olink">db_env_set_func_rename</a> 128 </p> 129 </li> 130 <li> 131 <p> 132 <a href="../api_reference/C/db_env_set_func_seek.html" class="olink">db_env_set_func_seek</a> 133 </p> 134 </li> 135 <li> 136 <p> 137 <a href="../api_reference/C/db_env_set_func_unlink.html" class="olink">db_env_set_func_unlink</a> 138 </p> 139 </li> 140 <li> 141 <p> 142 <a href="../api_reference/C/db_env_set_func_write.html" class="olink">db_env_set_func_write</a> 143 </p> 144 </li> 145 <li> 146 <p> 147 <a href="../api_reference/C/db_env_set_func_yield.html" class="olink">db_env_set_func_yield</a> 148 </p> 149 </li> 150 </ul> 151 </div> 152 <p>These interfaces are available only on POSIX platforms and from the 153Berkeley DB C language API.</p> 154 <p>A not-uncommon problem for applications is the new API in Solaris 2.6 155for manipulating large files. Because this API was not part of Solaris 1562.5, it is difficult to create a single binary that takes advantage of 157the large file functionality in Solaris 2.6, but still runs on Solaris 1582.5. <a class="ulink" href="solaris.txt" target="_top">Example code</a> that supports this is 159included in the Berkeley DB distribution, however, the example code was 160written using previous versions of the Berkeley DB APIs, and is only useful 161as an example.</p> 162 </div> 163 <div class="navfooter"> 164 <hr /> 165 <table width="100%" summary="Navigation footer"> 166 <tr> 167 <td width="40%" align="left"><a accesskey="p" href="program_compatible.html">Prev</a> </td> 168 <td width="20%" align="center"> 169 <a accesskey="u" href="program.html">Up</a> 170 </td> 171 <td width="40%" align="right"> <a accesskey="n" href="program_faq.html">Next</a></td> 172 </tr> 173 <tr> 174 <td width="40%" align="left" valign="top">Compatibility with historic UNIX interfaces </td> 175 <td width="20%" align="center"> 176 <a accesskey="h" href="index.html">Home</a> 177 </td> 178 <td width="40%" align="right" valign="top"> Programmer notes FAQ</td> 179 </tr> 180 </table> 181 </div> 182 </body> 183</html> 184