On Thursday 27 April 2006 14:36, Markus Henschel wrote:
> I did as much as I could to get to my problem so I can now place a
> new question here:
>
> Situation:
> suse linux 9.2
> mod_dav_svn 1.3.1
> Apache 2.0.50 and 2.2
> php4 4.4
>
> FSFS repository
> pre-commit hook:
> #!/bin/sh
> echo "test output" >&2
> exit 0
>
> Description:
> When any php4 script is executed the above pre-commit fails
> although this should not be possible. It cannot be a permission
> problem or something like that as the hooks are not failing
> immediately. They fail in an increasing ratio dependent on the
> usage of php scripts executed simultaneously on the server and the
> amount of commits that take place.
>
> I hacked the subversion sources a bit to get more output when a
> hook fails so I know for sure:
>
> 1. The hooks are executed as "test output" is given to a client
> when the hook fails.
>
> 2. The call to apr_proc_wait gives exitwhy==APR_PROC_EXET but an
> exit code that is a a fairly large number that is different every
> time a hook fails.
>
> 3. There are no hanging hook visible when doning `ps ax`
>
> So the hook gets executed but the exit code itproduces is not what
> apr_thread_proc returns. To make sure there is no problem with the
> shell on that system I used a binary program that did the same as
> the hook script above but it didn't change anything.
>
> I cannot imagine how this all is possible. What else can I do about
> it. I cannot reinstall the system as it is a production server. Any
> comments what else I could try are welcome.
Maybe I missed something, but that script should be...
#!/bin/sh
/bin/echo "test output" >&2
exit 0
...shouldn't it?
--
> Nick Thompson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 27 15:47:17 2006