[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

DB_CONFIG missing from my repo

From: Duncan McNaught <dmcnaught_at_symplified.com>
Date: Wed, 19 Mar 2008 14:32:21 -0600

Iıve search the archives and I canıt find anything for this question, which
would seem like Iım missing something simple:
There is no DB_CONFIG in my db directory. Using svn 1.4.6. Iıd like to
configure it to keep logs.
Iıve created a new repo with no flags, and still there is no DB_CONFIG in
the db directory.
What am I missing?

Fortunately, beginning with the 4.2 release of Berkeley DB, the database
environment has the ability to remove its own unused logfiles without any
external procedures. Any repositories created using an svnadmin which is
compiled against Berkeley DB version 4.2 or greater will be configured for
this automatic log file removal. If you don't want this feature enabled,
simply pass the --bdb-log-keep option to the svnadmin create command. If you
forget to do this, or change your mind at a later time, simple edit the
DB_CONFIG file found in your repository's db directory, comment out the line
which contains the set_flags DB_LOG_AUTOREMOVE directive, and then run
svnadmin recover on your repository to force the configuration changes to
take effect. See the section called ³Berkeley DB Configuration² for more
information about database configuration.

Duncan McNaught
Identity 2.0 Made Simple | Delivered On Demand
Received on 2008-03-19 21:33:29 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.