On Thu, Jun 11, 2009 at 09:55, Wiebesiek, Torsten
<torsten.wiebesiek_at_grecon.de> wrote:
>> From: David Weintraub [mailto:qazwart_at_gmail.com]
>> Sent: Thursday, June 11, 2009 3:36 PM
>>
>> What protocol are you using in your example? When you do a
>> checkout, you normally have to use a URL and not just a file name...
>
> Well, I've checked it with file and http protocol. I used the file
> protocol for testing on the server, and the http protocol from the
> windows machines.
>
>> Your repository must be owned by the user who is acting as a
>> server. If you're using the http protocol, this will be the
>> user who is running Apache. (Normally "apache" on Redhat" and
>> "wwwrun" on SUSE).
>
> The apache runs as wwwrun, the repositories including the hook
> scripts belong to wwwrun:www, the permissions of the hooks are
> 755:
>> ls -l post-commit
>> -rwxr-xr-x 1 wwwrun www 489 Jun 11 09:02 post-commit
>
>> I am assuming you're running the file:// protocol, and maybe
>> the hook scripts are not owned or executable by the user
>> running Apache.
>
> The hooks are working on the server using the file protocol.
> From the windows client using urls, they don't. The rest of
> the subversion access works just fine. It's possible to check
> out, commit changes, and so on.
>
> I have no idea, why the hooks work, using the file protocol on
> the server, and they don't from the windows clients using urls.
When you use file:///, the hooks execute as the user who's running the
commit operation.
Do you have any kind of secure environment set up that Apache is running under?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2361487
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-12 02:46:56 CEST