From owner-freebsd-questions@FreeBSD.ORG Fri Jun 29 13:54:41 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0FE816A46C for ; Fri, 29 Jun 2007 13:54:41 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 7459413C45B for ; Fri, 29 Jun 2007 13:54:41 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by ug-out-1314.google.com with SMTP id o4so375236uge for ; Fri, 29 Jun 2007 06:54:40 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=S3Vhq5KGhdZMj7k5eoggG+WevpbH6Q9lMuMwNzyr3KeTyO6C775FUiLqnYQDAyIcdYKjjgykPkZtye+wGOJHad//oMmix/8/xMgWYzMEEtbvARjtKxGhqFLO9CY3jqeir3nER/SZRHNHjO/eXTzMbIunQBZ8c9cXSGR0v/qjltM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=NzkDa5vUubLfzpF1LmA4hcca/9AQ9SNt8nzLMIu6Esi3C0ZTZf2Y0OqctXjz4ftPipO1935Rpp8GArGwI0ncs0pBFB+AmU1nBaxThCsApRiqKlIhalfM5OBZevdH+7IW7UgYVOWtzyGh01rKvzxBQw9ZnTk+hJTe8MK8SvzKcAI= Received: by 10.78.180.16 with SMTP id c16mr1627202huf.1183125280024; Fri, 29 Jun 2007 06:54:40 -0700 (PDT) Received: from ?IPv6:::ffff:127.0.0.1? ( [217.206.187.79]) by mx.google.com with ESMTP id k9sm17364610nfh.2007.06.29.06.54.38 (version=SSLv3 cipher=RC4-MD5); Fri, 29 Jun 2007 06:54:39 -0700 (PDT) From: Tom Evans To: Chad Perrin In-Reply-To: <20070629102318.GA11002@demeter.hydra> References: <20070628214550.GA7645@demeter.hydra> <20070628221018.GV17271@rescomp.berkeley.edu> <20070628224410.GA7877@demeter.hydra> <20070628232255.GW17271@rescomp.berkeley.edu> <20070629102318.GA11002@demeter.hydra> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-SPFUmk2V0OBiEVN1X9IN" Date: Fri, 29 Jun 2007 14:54:36 +0100 Message-Id: <1183125276.1511.54.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Cc: FreeBSD Questions Subject: Re: [SOLVED, sort of] Re: svn+ssh over nonstandard port fails to connect X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2007 13:54:42 -0000 --=-SPFUmk2V0OBiEVN1X9IN Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 2007-06-29 at 04:23 -0600, Chad Perrin wrote: > For a moment, I thought this wasn't going to work, because nothing like > that syntax seems to work in tcsh -- but then I remembered that, in this > case, the only reason I was even doing this was to test whether someone > else would be able to access the contents of the repository from > off-site, and that person is using bash. As such, I tried a pretty much > verbatim copy of what you suggested from a bash prompt, and it worked, so > it should work for him. >=20 > In other words, my immediate problem is solved. Thank you. >=20 > It seems odd that I cannot find an easier way around this with tcsh than > setting an environment variable, running the svn command I need, then > unsetting the environment variable, every time. Coupled with the strange > argument quoting requirements of tcsh and the fact that it's easier to > get into trouble with weird filenames than in other shells I've used, I'm > tempted to go back to bash. >=20 Did you miss Albert Shih's reply (slightly modified)? > Put something like > [tunnels] > myssh=3D/usr/bin/ssh -p 1234 123.45.678.90 > in=20 > ~/.subversion/config > and use > svn co svn+myssh://usr/home/svn-repos/project You can then clearly define as many transports as you like, which requires no setting of environment variables and is shell-agnostic. Full details are described in the redbook: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.s= erverconfig.svnserve.sshauth In fact, if you had read the svn+ssh portion of the redbook, you would have come across this sentence: "This example demonstrates a couple of things. First, it shows how to make the Subversion client launch a very specific tunneling binary (the one located at /opt/alternate/ssh) with specific options. In this case, accessing a svn+joessh:// URL would invoke the particular SSH binary with -p 29934 as arguments =E2=80=94 useful if you want the tunnel program = to connect to a non-standard port." Reading the manual is good. --=-SPFUmk2V0OBiEVN1X9IN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGhQ8clcRvFfyds/cRAkEPAKCw35HR72lV8JjCWgdYu2BseEmZ0wCfami6 bNm/An4Y618oWEFnc/DBfZo= =VZ5h -----END PGP SIGNATURE----- --=-SPFUmk2V0OBiEVN1X9IN--