Ben Collins-Sussman <sussman@collab.net> writes:
> I wonder if you're right, here, Eric. Sorry, didn't mean to ignore your
> older comments. The reason we decided to activate LOG_AUTOREMOVE by
> default was because we were getting endless complaints about the
> repository "getting too large" by people who had no idea how to clean
> them out. Correctly dminning a BDB repository is a real barrier to
> entry for so many newbies.
>
> There's a convenience/security tradeoff here.
>
> If we were to go back to the old way, where log files aren't
> autoremoved, what would our story to users be? "If you want to be
> perfectly secure, then you should allow your repository to fill up with
> logfiles, do a backup, then remove the unused logs. Automate this
> routine somehow."
>
> What do other developers think? Now that LOG_AUTOREMOVE is turned on,
> we're no longer getting endless complaints about disk space, but instead
> we're getting the occasional complaint about a BDB repository not being
> catastrophically recoverable, because logfiles are missing.
>
> Which path is the lesser of the evils?
An improved backup story (one that is easy, removes the logs, deals
with >2GB tables, etc) would be ideal, IMHO.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 14 22:45:13 2004