On Dec 15, 2004, at 6:57 AM, Gary Thomas wrote:
> I've modified my post-commit script to periodically do
> a complete repository dump. The repository is rather large;
> 700 or so revisions and the compressed dump is around 300MB.
> The odd thing is that the post-commit script fires up the
> dump (in the background so the client commit finishes right
> away). It then runs for a while (maybe 15 minutes) and then
> freezes up - just sits there. I have no troubles running
> the dump manually.
>
> I'm running this from Apache on Linux (Red Hat 9)
>
> Any ideas?
>
I have no idea about the freeze... but it seems pretty unwise to do
such a huge, time-consuming task in a post-commit script. What happens
if 3 commits all happen in the space of a minute?
If you're trying to design a backup strategy, you should probably do
something simpler and quicker in post-commit... like do an 'svnadmin
hotcopy' (which is quick, because it's basically like running 'cp -R'
on the repository)... or perhaps only dump just the newly committed
revision, so you end up with a bunch of incremental dumpfiles. Save
the 'full dump' stuff for a nightly cron job.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 15 14:49:42 2004