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. 3. [your idea here] Cheers, Daniel
