Justin Erenkrantz wrote:
>On Wed, Aug 07, 2002 at 10:02:24PM -0400, Sergey A. Lipnevich wrote:
>
>
>>a) Wait until perchild MPM stabilizes (an hour ago, it was still broken,
>>just tried building again, from the start get a lot of errors "[emerg]
>>(13)Permission denied: apr_proc_mutex_lock failed. Attempting to
>>shutdown process gracefully." and the same for ..._unlock), and run each
>>repository under separate user id;
>>
>>
>
>Well, no one has stepped up to support perchild MPM, so it is just
>sitting there and will sit there until someone wants it to work.
>
>
That's too bad :-(. I bet every smart hosting provider not willing with
to deal with su_exec would love to have perchild MPM to separate access
properly...
>
>
>>Why am I afraid of my own hook scripts? Because I'd like to allow over
>>
>>
>
>I would suggest a better solution would be to have your hook scripts
>execute sub-scripts with the appropriate permissions. This way your
>main script can become the user, do the chrooting, etc, etc. Your
>script wouldn't be under the control of the repository.
>
>That seems to me to be a better solution, but I dunno. -- justin
>
>
>
Thanks, that's very logical. Subversion calls a safe script, and it
chroot-s the rest. Thank you Justin!
--Sergey.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 11 00:50:14 2002