Greg Hudson <ghudson@MIT.EDU> writes:
> Let me try to ask this a little more forcefully: why do we have an
> svnadmin command to list all of the db logs? Does it do anything
> other than provide rope?
>
> The last time I asked this, all I got was a noncommittal answer from
> Fitz that it might help with an alternative implementation of hot
> backups, although I can't imagine how; there'd be a race condition
> between the time you ask the question and the time you finish copying
> the logs.
'svnadmin archive' was written to replace db_archive in admin's daily
routines because it ensure that the right version of Berkeley was
being used. Calls to 'svnnadmin recover' and 'svnadmin archive' then
replaced calls to db_recover and db_archive in hot-backup.py, but this
change was goofed up because hot-backup.py used *both* the "show all
logs" and the "show all unused logs" functionality. So now
hot-backup.py was broken. In order to get hot-backup.py working
again, we had to do one of two things a) revert the change that
introduced 'svnadmin archive' to the hot-backup.py script, or b) teach
'svnadmin' how to display both sets of log queries.
I went with a) as a stop-gap solution until b) was finished. B) is
now finished. Hot-backup.py can now be fixed to use svnadmin instead
of making the user know which DB utils to use.
Alternatively, we can roll the hot-backup.py functionality into an
'svnadmin copy' command, and then lose the 'list-dblogs' subcommand
altogether.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 25 18:23:12 2003