Re: [PATCH] Convert hot-backup.py.in to use new svnadmin list-dblogs and list-unused-dblogs commands

There's still the nasty little race in here where a log file that wasn't
backed up could be deleted, right? Like when the recovery step takes a
while and another commit comes in -- the new hotbackup hasn't had time
to copy yet, the current one finishes recovery and starts whacking log
files that it may not have copied.

I think that can be fixed by making sure only the log files that were
copied in step 3 are deleted in step 6 -- don't delete everything
db_archive reports, just the union of what it reports and what we copied...

Or am I missing something?

DJ

**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email
in error please notify the system manager.

This footnote also confirms that this email message has been
swept by MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 27 19:51:53 2003