Ryan Schmidt wrote:
> Phil Endecott wrote:
>> - Where do error messages from the hook scripts go? (Using Apache.)
> ...error messages go nowhere.
Not a great decision, I must say. How hard would it be to have them
appear in Apache's error log?
>> - I don't want this to slow down commits if I can help it. Is it OK
>> to background the hook script, i.e. to have "svn update &" in the
>> post-commit file?
>
> I would definitely recommend spawning off another process somehow, but
> simply "svn update &" may be too simplistic. If Bob commits r100 at
> 12:00:00 and the svn update process gets spawned at 12:00:01 and takes
> 10 seconds to complete, and Joe commits r101 at 12:00:02 firing off
> another svn update process at 12:00:03, then Joe's update process will
> probably throw an error that the working copy is in use / dirty /
> whatever it says
If the update instead waited for the working copy to be unlocked, rather
than failing immediately, there wouldn't be a problem. Is this an issue
only when the hook script is backgrounded, or does it also appy in the
normal case? Is there a lock somewhere that is not released until the
post-commit hook has finished? I had assumed that the locks were
released at the point of commit.
Cheers,
--Phil.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 9 22:30:59 2005