head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.56; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.08; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.57; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.07.59; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: log_file

log_file

 APIRef 

#include <db.h>


int
log_file(DB_ENV *env,
    const DB_LSN *lsn, char *namep, size_t len);

Description

The log_file function maps DB_LSN structures to filenames, copying the name of the file containing the record named by lsn into the memory location to which namep refers.

The len argument is the length of the namep buffer in bytes. If namep is too short to hold the filename, log_file will return ENOMEM. (Log filenames are normally quite short, on the order of 10 characters.)

This mapping of DB_LSN structures to files is needed for database administration. For example, a transaction manager typically records the earliest DB_LSN needed for restart, and the database administrator may want to archive log files to tape when they contain only DB_LSN entries before the earliest one needed for restart.

The log_file function returns a non-zero error value on failure and 0 on success.

Errors

The log_file function may fail and return a non-zero error for the following conditions:

ENOMEM
The supplied buffer was too small to hold the log filename.

The log_file 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 log_file function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

See Also

DB_ENV->set_lg_bsize, DB_ENV->set_lg_dir, DB_ENV->set_lg_max, DB_ENV->set_lg_regionmax, log_archive, log_compare, log_file, log_flush, log_get, log_put, log_register, log_stat, and log_unregister.

APIRef

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 d6 1 a6 1 Berkeley DB: DB_ENV->log_file d14 1 a14 1

DB_ENV->log_file

d25 1 a25 1 DB_ENV->log_file(DB_ENV *env, d29 1 a29 1

The DB_ENV->log_file function maps d35 1 a35 1 If namep is too short to hold the filename, DB_ENV->log_file will d47 1 a47 1

The DB_ENV->log_file function returns a non-zero error value on failure and 0 on success. d49 1 a49 1

The DB_ENV->log_file function may fail and return a non-zero error for the following conditions: d53 2 a54 2

The DB_ENV->log_file 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->log_file function may fail and return d62 1 a62 1 DB_ENV->log_archive, d64 6 a69 8 DB_ENV->log_cursor, DB_ENV->log_file, DB_ENV->log_flush, DB_ENV->log_put, DB_ENV->log_register, DB_ENV->log_stat, DB_ENV->log_unregister, DB_LOGC->close d71 1 a71 1 DB_LOGC->get. @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d29 1 a29 1

The DB_ENV->log_file method maps d47 1 a47 1

The DB_ENV->log_file method returns a non-zero error value on failure and 0 on success. d49 1 a49 1

The DB_ENV->log_file method may fail and return a non-zero error for the following conditions: d53 4 a56 6

The DB_ENV->log_file 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->log_file method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_LOGC, DB_LSN d58 16 a73 1 Logging Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d30 1 a30 1

The DB_ENV->log_file function maps d48 1 a48 1

The DB_ENV->log_file function returns a non-zero error value on failure and 0 on success. d50 1 a50 1

The DB_ENV->log_file function may fail and return a non-zero error for the following conditions: d54 6 a59 4

The DB_ENV->log_file 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->log_file function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d61 1 a61 16 DB_ENV->set_lg_bsize, DB_ENV->set_lg_dir, DB_ENV->set_lg_max, DB_ENV->set_lg_regionmax, DB_ENV->log_archive, log_compare, DB_ENV->log_cursor, DB_ENV->log_file, DB_ENV->log_flush, DB_ENV->log_put, DB_ENV->log_register, DB_ENV->log_stat, DB_ENV->log_unregister, DB_LOGC->close and DB_LOGC->get. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d29 1 a29 1

The DB_ENV->log_file method maps d47 1 a47 1

The DB_ENV->log_file method returns a non-zero error value on failure and 0 on success. d49 1 a49 1

The DB_ENV->log_file method may fail and return a non-zero error for the following conditions: d53 4 a56 6

The DB_ENV->log_file 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->log_file method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_LOGC, DB_LSN d58 16 a73 1 Logging Subsystem and Related Methods @