Date: Thu, 28 Jun 2007 16:22:55 -0700 From: Christopher Cowart <ccowart@rescomp.berkeley.edu> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: svn+ssh over nonstandard port fails to connect Message-ID: <20070628232255.GW17271@rescomp.berkeley.edu> In-Reply-To: <20070628224410.GA7877@demeter.hydra> References: <20070628214550.GA7645@demeter.hydra> <20070628221018.GV17271@rescomp.berkeley.edu> <20070628224410.GA7877@demeter.hydra>
next in thread | previous in thread | raw e-mail | index | archive | help
--Zgbii/ieujL2eaRx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 28, 2007 at 04:44:10PM -0600, Chad Perrin wrote: > On Thu, Jun 28, 2007 at 03:10:18PM -0700, Christopher Cowart wrote: > > On Thu, Jun 28, 2007 at 03:45:50PM -0600, Chad Perrin wrote: > > > I'm attempting to connect to a Subversion repository via SSH using a > > > nonstandard port to check out the repository. The names and numbers = in > > > the following have been changed to protect the guilty: > > >=20 > > > svn co svn+ssh://user@123.45.678.90:1234/usr/home/svn-repos/project= project > >=20 > > Try: > >=20 > > SVN_SSH=3D"ssh -p 1234" svn co svn+ssh://user@host/path >=20 > Are you suggesting setting an environment variable? I have more than one > repository checked out on this system, and they do not all use the same > port for access. This is the only way I know to do it. You don't have to set it in your shell's environment if you use this syntax to prefix the specific command. > > > The result I get is as follows: > > >=20 > > > ssh: 123.45.678.90:1234: hostname nor servname provided, or not kno= wn > > > svn: Connection closed unexpectedly > > >=20 > > > Am I having a brainless moment here? What am I missing? > >=20 > > ssh doesn't support the hostname:port syntax. You have to use -p. > >=20 > > Hope that helps, >=20 > I thought that might be the case, but I'm not sure how to specify it in > the svn command string -- which seems to be necessary since making a > universal (to this user account) configuration change would then break > access to other svn repositories. You can also create a "new" tunneling protocol. Look at the "SSH authentication and authorization" section of this part of the handbook: http://svnbook.red-bean.com/en/1.0/ch06s03.html Good luck, --=20 Chris Cowart Lead Systems Administrator Network Infrastructure, RSSP-IT UC Berkeley --Zgbii/ieujL2eaRx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFGhELPV3SOqjnqPh0RAvgtAJ9QKYLz0EC8jeHrl7qynvSxqFlj6gCgwBuZ HSvvkwotmY+VkSpzdrDdZWI= =Lsge -----END PGP SIGNATURE----- --Zgbii/ieujL2eaRx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070628232255.GW17271>