Re: Subversion checkin problem

Ryan Schmidt wrote:
> The client will wait for the post-commit hook to finish on the server.
> There's really no point to this, since it's not like the post-commit
> hook can send any info to the client or affect the client in any way.
> But the client still waits. And sometimes you see errors as a result.
> Commit-mail scripts can sometimes take a long time, if the revision is
> large and they have been asked to put the diff of the commit into the
> email. To ensure your post-commit hook finishes quickly in any case,
> fork any other tasks off into new processes, like this:
>
> /usr/share/subversion/hook-scripts/commit-email.pl "$REPOS" "$REV"
> --diff n -h 3dnature.com -s "svn commit:" devs@3dnature.com >/dev/null
> 2>/dev/null &

   Ok. I have done this now. It might be a good idea to change the post-commit template in
the distribution to suggest this. What is the client timeout? Is there a reason the client
aborts and corrupts the working directory if the server times out? Seems like a design
ripe for problems.

   If the client times out waiting for the server to run the post-commit, what operation
exactly does the client fail to complete? Is it something I can fix manually by some
supported process? I can do a fresh checkout on my working dir just fine, though slowly.

   Thanks for the advice.

-- 
      Chris 'Xenon' Hanson | Xenon @ 3D Nature | http://www.3DNature.com/
  "I set the wheels in motion, turn up all the machines, activate the programs,
   and run behind the scenes. I set the clouds in motion, turn up light and sound,
   activate the window, and watch the world go 'round." -Prime Mover, Rush.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org