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

Re: What happens after hook "post-commit"

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-06-05 14:49:27 CEST

Michael Schmitt <schmitt@TI.Uni-Trier.DE> writes:

> Hello,
> I have added a few echo statements in hook "post-commit" that print
> some messages on the console. Surprisingly, it takes another 1 to 2
> seconds until svn prints the final "Committed revision XXX.".
> What happens in between? (I notice some hard disk activity.) Is svn
> lying and "post-commit" is not really the last action of a "commit"?

The commit finishes in the repository, creating revision XXX. Then,
if a post-commit hook exists, the program is fork()ed and passed the
newly created revision number.

The new 1-2 second delay you're seeing is probably the time it takes
to fork() a child process and wait for the child process to die. If
you don't want the parent process to wait for everything in your hook
script to return, try backgrounding (&) the commands in the script.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 5 14:51:09 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.