Mark Phippard wrote:
> On Tue, Jul 15, 2008 at 11:39 AM, Sergey Proskurnya <alaley_at_gmail.com> wrote:
>
>> I've examined write-through proxy feature and
>> found that the state of Slave server could be easily
>> de-synchronized (against the repo state of Master-server).
>>
>> I've figure out that if someone commits to Master while
>> there is no connection between Slave and Master (ISP failure?),
>> then sample post-commit hook fails to synchronize repo state.
>> And after such event, all subsequent attempts will fail because
>> incremental "dump load" will fail also (or Slave will just loose one
>> revision?)
>
> I'd suggest you use svnsync to maintain the slave. It will be smart
> enough to send all revisions it is missing. I think the examples were
> written while svnsync was still in development.
>
I just looked in the book and that appears to be more up to date on this
issue than the release notes. The release notes do kind of suggest that
dump/load is the preferred method ("svnsync can probably do the same thing")
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-15 19:27:06 CEST