Mark K <mark_at_mitsein.net> writes:
> The main reason that I was looking for an answer to this is that I
> wrote my own verison of fsfs-reshard since fsfs-reshard.py is marked as
> not fit for production. I wrote one in perl that doesn't attempt to
> handle as many cases as the original fsfs-reshard.py does but I wanted
> to add some sort of locking mechanism to it.
>
> At any rate, I did my upgrade last week and just ran svnadmin
> upgrade /svn/repos && fsfs-reshard.pl /svn/repos on all of my
> repositories and crossed my fingers :). Nothing went wrong, but it
> would be nice to improve the script with some locking.
Or better yet, an 'svnadmin lock' command, that would make the
repository readable but not writeable until 'svnadmin unlock' is
issued. (If someone wants a repository to be neither writeable nor
readable, they can just shut off access at the RA layer -- turn off
svnserve, httpd, whatever.)
I'll ask why fsfs-reshard.py is considered unready for production use,
on dev@.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-10 17:24:19 CEST