Perry E. Metzger wrote:
> Brian Mathis <bmathis@directedge.com> writes:
>
>>The point is that there are already TWO other options that will allow
>>you to reach the goal you want. 1 is apache, and 2 is svnserve.
>>Using these requires ZERO code changes to svn. If apache doesn't meet
>>your needs, then fine, use svnserve over ssh.
>
>
> How about I drop using svn instead.
>
> Actually, I won't do that -- but please bear in mind that ignoring
> people's needs doesn't encourage people to use a program.
>
> So anyway, explain to me exactly how it is that svn+ssh works. What
> exactly is being invoked over the ssh connection? I was under the
> impression it WAS svnserve, just being run to stdout instead of over a
> socket. Why is this, plus setgid or something, a bad idea in any way?
It is svnserve, just run in tunnel mode as the user who ssh'd in. I
don't know what Brian is talking about. As for running it setgid, feel
free to give it a shot, I don't know if anyone has tried that approach.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 13 19:59:33 2004