Re: Problem connecting to svnserve - not sure about protocols?

On Dec 18, 2006, at 13:12, Jon Koerber wrote:

> I do have a firewall running on my server, but it looks like SSH
> runs on port 22 on Mac OS X Tiger. Just in case, I added an allow
> rule for port 3690 and tried the command again with no luck. I
> then turned off the server's firewall entirely to test the
> connection and still get the same error as above. Hmm, this is
> perplexing. Did I miss something in the build?

When using svn+ssh://, yes, you'd be using port 22. But when using
the svn:// protocol, you'd be using the svnserve port 3690.

svn:// and svn+ssh:// work differently. svn:// connects over 3690 to
a running svnserve daemon on the server. svn+ssh:// does not make use
of any running daemon; rather, it starts svnserve itself every time
you connect, and stops it when you're done. So svnserve needs to be
in the path of the connecting user. It isn't, hence the error that it
can't find the command svnserve.

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org