Re: Script for creating a large repository

Karl Fogel wrote:

>Branko Čibej <brane@xbc.nu> writes:
>
>
>>For various unrelated reasons, I'm working on adding database
>>configuration flags to "svnadmin create". When I'm done, nobody will
>>have to edit the DB_CONFIG file after creating the repo. I suppose I
>>could also add a generic descriptive flag; --repo-size=humongous, or
>>some such. :-)
>>
>>
>
>Do you mean adding options to 'svnadmin create' that cause various
>things to happen in DB_CONFIG? In that case, that doesn't change the
>question of what the default configuration should be. When someone
>just runs
>
> $ svnadmin create foo
>
>... what should be in `foo/db/DB_CONFIG'?
>
>(Also, why do you say that nobody will have to edit DB_CONFIG after
>creating the repo. 'svnadmin create' is only run at creation time,
>but people might still need to tune their repositories as needs
>change, no?)
>
>I'm getting the feeling I've misunderstood your post, but I can't
>figure out how :-). Please enlighten.
>
>

My point is that instead of doing what Brandon suggested (that is, write
a script that modifies DB_CONFIG right after it's been created), you'd
just pass an option to "svnadmin create" and it would create the config
file with the appropriate sizes. Of course, you might have to edit
DB_CONFIG later during the lifetime of the repository -- I don't propose
to write "svnadmin tune" command that modifies existing DB_CONFIG files
:-) -- but usually you'll have a pretty good idea about how big your
repository will be, and will create it with the appropriate options.

Someday we may even have "svnadmin tune", but I don't need it now, so I
won't write it. :-)

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org