From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/program_runtime.html | 130 +++++++++---------------- 1 file changed, 47 insertions(+), 83 deletions(-) (limited to 'docs/programmer_reference/program_runtime.html') diff --git a/docs/programmer_reference/program_runtime.html b/docs/programmer_reference/program_runtime.html index b3cd0f07..ee3376b8 100644 --- a/docs/programmer_reference/program_runtime.html +++ b/docs/programmer_reference/program_runtime.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +
Prev Chapter 15.  - Programmer Notes - Chapter 15.  Programmer Notes  Next
@@ -38,130 +36,95 @@
-

It is possible for applications to configure Berkeley DB at run-time to -redirect Berkeley DB library and system calls to alternate interfaces. For -example, an application might want Berkeley DB to call debugging memory -allocation routines rather than the standard C library interfaces. The -following interfaces support this functionality:

+

+ It is possible for applications to configure Berkeley DB at + run-time to redirect Berkeley DB library and system calls to + alternate interfaces. For example, an application might want + Berkeley DB to call debugging memory allocation routines + rather than the standard C library interfaces. The following + interfaces support this functionality: +

-

These interfaces are available only on POSIX platforms and from the -Berkeley DB C language API.

-

A not-uncommon problem for applications is the new API in Solaris 2.6 -for manipulating large files. Because 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 still runs on Solaris -2.5. Example code that supports this is -included in the Berkeley DB distribution, however, the example code was -written using previous versions of the Berkeley DB APIs, and is only useful -as an example.

+

+ These interfaces are available only on POSIX platforms and + from the Berkeley DB C language API. +

+

+ A not-uncommon problem for applications is the new API in + Solaris 2.6 for manipulating large files. Because 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 still runs on Solaris 2.5. Example code that supports this + is included in the Berkeley DB distribution, however, the + example code was written using previous versions of the + Berkeley DB APIs, and is only useful as an example. +

@@ -178,7 +141,8 @@ as an example.

Home -  Performance Event Monitoring +  Performance Event + Monitoring
-- cgit v1.2.1