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

Re: svn+ssh://: preventing post-commit from running

From: Branko ─îibej <brane_at_apache.org>
Date: Sat, 22 Oct 2016 16:03:47 +0200

On 22.10.2016 14:28, Daniel Shahaf wrote:
> Daniel Shahaf wrote on Sat, Oct 22, 2016 at 12:18:23 +0000:
>> When using svn+ssh://, if the ssh session is killed whilst rep-cache.db
>> is being written to, then the post-commit hook won't run.
> Possible mitigations:
>
> 1. Write a daemon that watches the db/current file, and whenever that file
> changes, runs the post-commit hook.
>
> That will solve not only the problem at hand but also the "post-commit hooks
> may run out of sequence" problem.
>
> 2. When we're in svnserve -i/-t mode, fork() before moving db/current
> into place, and arrange for the child not to be killed by SIGHUP to the
> parent.

This sounds like it /should/ be moderately easy to do ...

-- Brane
Received on 2016-10-22 16:03:52 CEST

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