db_env_set_func_unmap
db_env_set_func_unmap |
|
#include <db.h>int db_env_set_func_unmap(int (*func_unmap)(void *addr, size_t len));
The Berkeley DB library requires the ability to unmap a file or shared memory region from memory. The func_unmap argument must conform to the following interface:
int unmap(void *addr, size_t len);
The addr argument is the argument returned by the db_env_set_func_map function when the file or region was mapped into memory, and the len argument is the same as the len argument specified to the db_env_set_func_map function when the file or region was mapped into memory.
The func_unmap function must return the value of errno on failure and 0 on success.
The db_env_set_func_unmap interface affects the entire application, not a single database or database environment.
Although the db_env_set_func_unmap interface may be used to configure Berkeley DB at any time during the life of the application, it should normally be called before making any calls to the db_env_create or db_create functions.
The db_env_set_func_unmap function returns a non-zero error value on failure and 0 on success.
The db_env_set_func_unmap function may fail and return a non-zero error for the following conditions:
The db_env_set_func_unmap function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the db_env_set_func_unmap function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
|
|
Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d37 1 a37 1
The func_unmap interface must return the value of errno on d39 6 a44 7
The db_env_set_func_unmap method configures all operations performed by a process and all of its threads of control, not operations confined to a single database environment.
Although the db_env_set_func_unmap interface may be called at any time during the life of the application, it should normally be called before making calls to the db_env_create or db_create methods.
The db_env_set_func_unmap method returns a non-zero error value on failure and 0 on success. d46 1 a46 1
The db_env_set_func_unmap method may fail and return a non-zero error for the following conditions: d50 4 a53 4
The db_env_set_func_unmap method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the db_env_set_func_unmap method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d55 19 a73 1 Run-time configuration @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d38 1 a38 1
The func_unmap function must return the value of errno on d40 7 a46 6
The db_env_set_func_unmap interface affects the entire application, not a single database or database environment.
Although the db_env_set_func_unmap interface may be used to configure Berkeley DB at any time during the life of the application, it should normally be called before making any calls to the db_env_create or db_create functions.
The db_env_set_func_unmap function returns a non-zero error value on failure and 0 on success. d48 1 a48 1
The db_env_set_func_unmap function may fail and return a non-zero error for the following conditions: d52 4 a55 4
The db_env_set_func_unmap function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the db_env_set_func_unmap function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d57 1 a57 19 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, and db_env_set_func_yield. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d37 1 a37 1
The func_unmap interface must return the value of errno on d39 6 a44 7
The db_env_set_func_unmap method configures all operations performed by a process and all of its threads of control, not operations confined to a single database environment.
Although the db_env_set_func_unmap interface may be called at any time during the life of the application, it should normally be called before making calls to the db_env_create or db_create methods.
The db_env_set_func_unmap method returns a non-zero error value on failure and 0 on success. d46 1 a46 1
The db_env_set_func_unmap method may fail and return a non-zero error for the following conditions: d50 4 a53 4
The db_env_set_func_unmap method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the db_env_set_func_unmap method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d55 19 a73 1 Run-time configuration @