m4_comment([$Id: config.so,v 10.20 2006/08/30 10:08:16 bostic Exp $])m4_ref_title(Logging Subsystem,    Configuring logging, @logging configuration, log/intro, log/limits)m4_p([dnlThe aspects of logging that may be configured are the size of thelogging subsystem's region, the size of the log files on disk and thesize of the log buffer in memory.  The m4_refT(dbenv_set_lg_regionmax)specifies the size of the logging subsystem's region, in bytes.  Thelogging subsystem's default size is approximately 60KB.  This value mayneed to be increased if a large number of files are registered with them4_db log manager, for example, by opening a large number of m4_dbdatabase files in a transactional application.])m4_p([dnlThe m4_refT(dbenv_set_lg_max) specifies the individual log file size forall the applications sharing the m4_db environment.  Setting the logfile size is largely a matter of convenience and a reflection of theapplication's preferences in backup media and frequency.  However,setting the log file size too low can potentially cause problems becauseit would be possible to run out of log sequence numbers, which requiresa full archival and application restart to reset.  Seem4_link(M4RELDIR/ref/log/limits, [Log file limits]) for moreinformation.])m4_p([dnlThe m4_refT(dbenv_set_lg_bsize) specifies the size of the in-memory logbuffer, in bytes.  Log information is stored in memory until the bufferfills up or transaction commit forces the buffer to be written to disk.Larger buffer sizes can significantly increase throughput in thepresence of long-running transactions, highly concurrent applications,or transactions producing large amounts of data.  By default, the bufferis approximately 32KB.])m4_page_footer