John:
This is most likely caused by the fact that the commit is being
performed as a different user (I think it's wwwrun on sles) and with
a different environment. Since I don't know what all your hook
scripts are doing, it's kind of hard to pinpoint, but here are some
things to check on:
1. Does the wwwrun user have the rights to execute the hook script
and anything the hook script calls?
2. Do you make any assumptions regarding environment variables such
as PATH within the script? Some environment variable modifications
which may not be available from the shell when kicked off by commit
done via http.
Hope that helps.
Cheers,
-craig
On Mar 4, 2006, at 7:42 AM, John Waycott wrote:
> Our main subversion system at work has a weird issue. The commit
> messages stopped working a few days ago. What we determined is that
> hook scripts execute normally when we use svn or file access, but
> the scripts do not run when we use http access. There are no errors
> in the apache error log or anything unusual in the access log.
>
> It doesn't make sense to me that hook scripts would fail for a
> specific access protocol. The commits all happen normally
> regardless of the protocol used. There have been no changes to the
> apache server that I'm aware of. We're using Subversion 1.3.0 on
> Suse Linux enterprise 9. Subversion was compiled from source - we
> are not using the pre-configured RPMs.
>
> Any ideas where I can look? We are considering a re-install of
> Subversion to see if that corrects the issue but I would like to
> know the cause of the problem first.
>
> -- John Waycott
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 4 15:28:49 2006