RE: post-commit & hot-backup.py

> From: Blair Zajac [mailto:blair@orcaware.com]
> Sent: 18 July 2002 07:42

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

From post-commit AFAIK.

> 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?

IMO, yes.

> Is the repository modified at any point after post-commit is called?

Shouldn't be [other than due to the next commit ;]

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

I know I run in it in the background, no sleep, since it is post-commit
and the commit of a single revision was completed. Running the backup
at that point ensures you get a backup that includes the committed
revision. Running it in the background will also make your post-commit
hook return control back to mod_dav_svn sooner.
 
> Blair

Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 18 09:31:56 2002