m4_comment([$Id: runtime.so,v 10.36 2006/06/08 13:04:29 bostic Exp $])m4_ref_title(Programmer Notes,    Run-time configuration,, program/compatible, program/faq)m4_p([dnlIt is possible for applications to configure m4_db at run-time toredirect m4_db library and system calls to alternate interfaces.  Forexample, an application might want m4_db to call debugging memoryallocation routines rather than the standard C library interfaces.  Thefollowing interfaces support this functionality:])m4_indent([dnlm4_ref(dbenv_set_func_close)m4_ref(dbenv_set_func_dirfree)m4_ref(dbenv_set_func_dirlist)m4_ref(dbenv_set_func_exists)m4_ref(dbenv_set_func_free)m4_ref(dbenv_set_func_fsync)m4_ref(dbenv_set_func_ftruncate)m4_ref(dbenv_set_func_ioinfo)m4_ref(dbenv_set_func_malloc)m4_ref(dbenv_set_func_map)m4_ref(dbenv_set_func_open)m4_ref(dbenv_set_func_pread)m4_ref(dbenv_set_func_pwrite)m4_ref(dbenv_set_func_read)m4_ref(dbenv_set_func_realloc)m4_ref(dbenv_set_func_rename)m4_ref(dbenv_set_func_seek)m4_ref(dbenv_set_func_sleep)m4_ref(dbenv_set_func_unlink)m4_ref(dbenv_set_func_unmap)m4_ref(dbenv_set_func_write)m4_ref(dbenv_set_func_yield)])m4_p([dnlThese interfaces are available only on POSIX platforms and from them4_db C language API.])m4_p([dnlA not-uncommon problem for applications is the new API in Solaris 2.6for manipulating large files.  Because this API was not part of Solaris2.5, it is difficult to create a single binary that takes advantage ofthe large file functionality in Solaris 2.6, but still runs on Solaris2.5.  m4_linkweb(solaris.txt, [Example code]) that supports this isincluded in the m4_db distribution, however, the example code waswritten using previous versions of the m4_db APIs, and is only usefulas an example.])m4_page_footer