e.huelsmann@gmx.net wrote:
>ehh, Ben, the faq item first describes the pre 0.24.2 situation and then the
>current one. Maybe that should be reversed to avoid problems and questions?
How about this?
Index: www/project_faq.html
===================================================================
--- www/project_faq.html (revision 6929)
+++ www/project_faq.html (working copy)
@@ -635,30 +635,29 @@
repository from the day it was born. But in practice, if you're
making backups, it's probably not worth the cost in disk space.</p>
-<p>Run the <code>db_archive</code> command in the db/ area to see
+<p>Use <code>svnadmin</code> to see
which log files can be deleted. You may want a cron job to do this.</p>
<pre>
-$ db_archive -a -h /repos/db
+$ svnadmin list-unused-dblogs /repos
/repos/db/log.000003
/repos/db/log.000004
[...]
-$ db_archive -a -h /repos/db | xargs rm
+$ svnadmin list-unused-dblogs /repos | xargs rm
# disk space reclaimed!
</pre>
-<p>Or, if you are running a Subversion release <em>later</em> than
-0.24.2, then there's no need to locate the correct
-<code>db_archive</code> command or set of arguments. Just use
-<code>svnadmin</code>:</p>
+<p>You could instead use Berkeley DB's <code>db_archive</code> command:</p>
<pre>
-$ svnadmin list-unused-dblogs /repos | xargs rm
+$ db_archive -a -h /repos/db | xargs rm
# disk space reclaimed!
</pre>
+<p>See also <code>svnadmin copy</code> or <code>hotbackup.py</code>.</p>
+
<![CDATA[=========================================================]]>
>>Steven Op de beeck <annika@ulyssis.org> writes:
>>>Why did my repo got so huge?
>>
>>Read the FAQ about this:
>>
>> http://subversion.tigris.org/project_faq.html#bdblogs
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 31 14:33:00 2003