OS: Debian sarge (upgraded to 2.6.13 kernel)
If you want, you can send me the post-commit script and I'll take a
On Wed, 2006-02-08 at 12:48 -0800, Kedzierski, Artur CIV
NAVSURFWARCENDIV CORONA wrote:
> What OS and version of Apache/Subversion are you using?
> -----Original Message-----
> From: Josh Kuo [mailto:email@example.com]
> Sent: Wednesday, February 08, 2006 11:53
> To: firstname.lastname@example.org
> Subject: RE: Subversion clients wait for post-commit to finish
> I tried the same thing in my post-commit script and I don't get a 20
> second delay.
> On Wed, 2006-02-08 at 11:40 -0800, Kedzierski, Artur CIV
> NAVSURFWARCENDIV CORONA wrote:
> > Unfortunately, that didn't do the trick.
> > I tried:
> > sleep 20 > /dev/null 2>&1 &
> > and committing a file still pauses for 20 seconds.
> > -----Original Message-----
> > From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of Garrett
> > Rooney
> > Sent: Wednesday, February 08, 2006 11:18
> > To: Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA
> > Cc: email@example.com
> > Subject: Re: Subversion clients wait for post-commit to finish
> > On 2/8/06, Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA
> > <firstname.lastname@example.org> wrote:
> > > I have a post-commit hook script that fires up
> > > an automatic compilation. The problem is that when
> > > a client (TortoiseSVN on Windows or Subversion on Linux)
> > > do a commit, the client waits for the post-commit to
> > > finish. I even put the compilation process in the background
> > > (e.g. compile_project&). It still waits for the process
> > > to finish. How can I get around that? The compilation
> > > process takes a while. I tried using bash's 'disown'
> > > function but that doesn't help either.
> > > To duplicate a problem, put 'sleep 20' in your
> > > post-commit hook script. Then do a commit. The commit
> > > will hang for 20 seconds on 'Transmitting file data .'
> > > step.
> > > I run Subversion 1.3 on Apache 2.0.55 on Slackware
> > > 10.2.
> > > I appreciate any help.
> > You need to make sure that the backgrounded job closes its stdout and
> > stderr filehandles. Something like:
> > my-process > /dev/null 2>&1 &
> > Once that is done, the process should be backgrounded correctly.
> > -garrett
Josh Kuo <email@example.com>
Received on Wed Feb 8 22:11:48 2006