1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
<! "@(#)runtime.so 10.5 (Sleepycat) 12/1/98">
<!Copyright 1997, 1998 by Sleepycat Software, Inc. All rights reserved.>
<html>
<body bgcolor=white>
<head>
<title>Berkeley DB Reference Guide: Programmer Notes</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btr
ee,hash,hashing,transaction,transactions,locking,logging,access method,access me
thods,java,C,C++">
</head>
<h3>Berkeley DB Reference Guide: Programmer Notes</h3>
<p>
<h1 align=center>Run-time configuration</h1>
<p>
There are two main ways of configuring Berkeley DB at run-time. The first is
<a href="../../api_c/internal/db_jump_set.html">db_jump_set</a>, which allows applications to intercept Berkeley DB
requests for underlying library or system call functionality. The second
is <a href="../../api_c/internal/db_value_set.html">db_value_set</a> which allows applications to re-configure, on an
application-wide basis, Berkeley DB behaviors.
<p>
The <a href="../../api_c/internal/db_jump_set.html">db_jump_set</a> and <a href="../../api_c/internal/db_value_set.html">db_value_set</a> interfaces are only
available from the C API.
<p>
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 run on Solaris 2.5. Example
code that allows this, using the <a href="../../api_c/internal/db_jump_set.html">db_jump_set</a> interface, is included
<a href="solaris.txt">here</a>.
<p>
<a href="../../ref/program/convert.html"><img src="../../images/prev.gif"></a>
<a href="../../ref/toc.html"><img src="../../images/toc.gif"></a>
</tt>
</body>
</html>
|
