post-commit & hot-backup.py

How does svn.collab.net run hot-backup.py? Via cron?

Given the core dump we've been seeing when post-commit fails in the
server, it seems to me that post-commit does not run at the complete
end of the commit, i.e. there's stuff that happens afterwords,
otherwise why would the core dump happen.

So the question is, is it a good idea to run hot-backup.py from
post-commit? Is the repository modified at any point after
post-commit is called?

Maybe the safe way to run hot-backup.py from post-commit is to
background it with a 60 second sleep.

Blair

-- 
Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org