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

[PATCH] Re: Story of BerkeleyDB failing

From: Rafael Garcia-Suarez <raphel.garcia-suarez_at_hexaflux.com>
Date: 2002-12-09 10:48:20 CET

"Sander Striker" <striker@apache.org> wrote:
> > From: Branko Cibej [mailto:brane@xbc.nu]
> >>
> > Right, this should be a FAQ: Every time you change DB_CONFIG, you have
> > to run svnadmin recover, otherwise the changes don't take effect.
>
> We should put it in the comment lines in the prefabricated
> DB_CONFIG file we put in the repository.

Here's a small patch :

* subversion/libsvn_fs/fs.c
    Add a comment in the default DB_CONFIG file about 'svnadmin recover'
    needed whenever it's modified.

--- subversion/libsvn_fs/fs.c.orig Mon Dec 9 10:42:07 2002
+++ subversion/libsvn_fs/fs.c Mon Dec 9 10:44:16 2002
@@ -431,6 +431,8 @@ svn_fs_create_berkeley (svn_fs_t *fs, co
     static const char dbconfig_contents[] =
       "# This is the configuration file for the Berkeley DB environment\n"
       "# used by your Subversion repository.\n"
+ "# You must run 'svnadmin recover' whenever you modify this file\n"
+ "# for your changes to take effect.\n"
       "\n"
       "### Lock subsystem\n"
       "#\n"
End of Patch.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 9 10:54:01 2002

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