The LogConfig type exposes the following members.
Serves as a hash function for a particular type.(Inherited from Object.)
Gets the Type of the current instance.(Inherited from Object.)
If true, Berkeley DB will automatically remove log files that are no longer needed.
The path of a directory to be used as the location of logging files. Log files created by the Log Manager subsystem will be created in this directory.
If true, Berkeley DB will flush log writes to the backing disk before returning from the write system call, rather than flushing log writes explicitly in a separate system call, as necessary.
If true, maintain transaction logs in memory rather than on disk.
If true, turn off system buffering of Berkeley DB log files to avoid double caching.
If true, zero all pages of a log file when that log file is created.
The size of the in-memory log buffer, in bytes.
The absolute file mode for created log files.
The initial number of log identifier entities created by the Berkeley DB environment
The maximum size of a single file in the log, in bytes. Because Offset is an unsigned four-byte value, MaxFileSize may not be larger than the maximum unsigned four-byte value.
Te size of the underlying logging area of the Berkeley DB environment, in bytes.