kfogel@collab.net wrote:
>I don't really buy the argument for keeping the logs. Just because
>Berkeley DB happens to offer this incredibly detailed audit and
>recovery trail, doesn't mean we have to take advantage of it. CVS
>doesn't even support such a thing. What are the circumstances where a
>regular backup schedule with 'svnadmin hotcopy' is insufficient and
>one would actually need these space-eating logs? Are such
>circumstances common enough to warrant turning on the space-eating by
>default?
>
>
I'd rather the logs were cleaned up by default -- anyone who cares about
integrity is going to read the book section on "backing up your
repository" and sort their backup procedures (this is the first section
I read after getting the repos working, and now I do a daily dump). If
that's not good enough, docs should (and I think already do) include
bits about ultra-paranoia style hot backups and the like. Maybe that
section is where switching log retention back on could be described.
Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 27 11:04:36 2003