Re: Getting exclusive access to the repository

Philip Martin philip@codematters.co.uk writes:

 There is still a gap between the time the administrator verifys that
 there are no processes accessing the database, and 'svnadmin recover'
 taking the lock; during this gap another process could start. At
 present some other mechanism is needed to close this gap, perhaps you
 unplug the network cable.

Sure, unplugging the network cable works. All you really need do
is shut down the access mechanism. That could be chmod 0 repo,
chmod 0 svnserve, apachectl stop, or unplugging the network
cable. It all depends on what mechanisms people use to get to
the repo. There is no missing functionality here.

 It would be better if one could a) lock the database and
 prevent new conections, then b) wait for the administrator to
 verify that there are no existing connections, and finally c)
 run recover.

What's the point? This is already easily done.

--
Eric Gillespie * epg@pretzelnet.org

Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:10:45 2006