[prev in list] [next in list] [prev in thread] [next in thread] 

List:       puppet-users
Subject:    Re: [Puppet-users] SVN commit hook checks
From:       Kevin Fox <Kevin.Fox () pnl ! gov>
Date:       2007-03-29 23:14:44
Message-ID: 1175210084.13228.14.camel () zathras ! emsl ! pnl ! gov
[Download RAW message or body]

If I had to venture a guess, I'd say its whatever your OS's pipe buffer
size, but I don't know for sure. I suspect svn just waits for a return
code, and the app is blocking until svn reads from the buffer that never
happens. If that's really the case, I think you can check to see if the
write will block and just exit at that point.

Kevin

On Thu, 2007-03-29 at 15:56 -0700, Chris McEniry wrote:
> > When I was writing my variant of the commit hook, I discovered svn has a
> > bug (feature? :) that if stderr is too big, the commit hook will pause
> > indefinitely. So, returning all of the error stuff in one pass rather
> > then stopping at the first file with an error may not be as safe.
> 
> Strange, I think I noticed that when I was working up the commit script,
> but I didn't notice it enough to pick up on why.  I'm assuming it's a
> buffer issue, but eh.
> 
> Do you happen to immediately know what the limit it?  I can look or
> test, but figured I'd ask first.  If I know the limit, I can update
> the commit hook I posted to truncate if needbe.
> 
> Thanks,
> --mac
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users

[prev in list] [next in list] [prev in thread] [next in thread]