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

Re: repository on client is newer than on server as a result of server hd failure

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-02-08 23:16:48 CET

On Feb 8, 2006, at 20:12, Josh Kuo wrote:

> Not sure if this helps you, I have a post-commit hook script that
> backs
> up the repository, so I know I always have the most up-to-date backup.
> Here's a overly simplified version writtien in shell:
> <post-commit>
> #!/bin/sh
> svnadmin dump "$1" > /home/backups/backup.svndump &
> </post-commit>
> I discovered that my commit was taking a while because of the dump,
> so I
> put the process in the background (with the & symbol), so there's no
> delay when users commit new revisions.

And what happens if two users commit changes one right after one the
other? I'd expect the two dump processes together to clobber the
dumpfile. Doesn't sound like such a great strategy, unless you've
built in some mechanism that you're not showing that ensures only one
dump process runs at a time.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 8 23:18:37 2006

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.