[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: is 'svn lock' possible for replication?

From: Steven Woody <narkewoody_at_gmail.com>
Date: Thu, 2 Sep 2010 10:05:49 +0800

On 23 August 2010 19:18, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Campbell Allan wrote on Mon, Aug 23, 2010 at 11:10:28 +0100:
>>
>> On Sunday 22 Aug 2010, Andy Levy wrote:
>> > On Sun, Aug 22, 2010 at 14:16, Steven Woody <narkewoody_at_gmail.com> wrote:
>> > > On 20 August 2010 23:19, Steven Woody <narkewoody_at_gmail.com> wrote:
>> > >> Hi,
>> > >>
>> > >> With a replication/write-through setup, can a user execute 'svn lock'
>> > >> on master/slaver nodes? Thanks.
>> > >
>> > > Hey folks, no one can gives me a hint?
>> >
>> > You asked at the beginning of a weekend and no one is obligated to
>> > reply within a set timeframe (or at all, for that matter). If you need
>> > an answer that fast, it costs you nothing to set up a master/slave
>> > pair to test it for yourself (and you'd be done by now if you'd
>> > started Friday).
>>
>> I mentioned in your previous thread their isn't support in svnsync and this
>> would require a third party script to maintain the locks.
>
> Yeah, either the pre-lock hook on the mirror could run 'lock' on the
> master manually, or someone could go ahead and patch mod_dav_svn to do
> that directly in the C code.
>
> I'm pretty sure I saw/heard of such a pre-lock hook somewhere...
>
> Daniel
>

Thank you everyone. Maybe I really need to do some tests. I think
there is no problem to setup multiple instances of subversion. I did
not do experiment before is because that server is really serious one.

-- 
Life is the only flaw in an otherwise perfect nonexistence
    -- Schopenhauer
narke
public key at http://subkeys.pgp.net:11371 (narkewoody@gmail.com)
Received on 2010-09-02 04:06:26 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.