Re: [SOLVED, sort of] Re: svn+ssh over nonstandard port fails to connect

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.

In other words, my immediate problem is solved. Thank you.

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.


Did you miss Albert Shih's reply (slightly modified)?

Put something like
[tunnels]
myssh=/usr/bin/ssh -p 1234 123.45.678.90
in
~/.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.serverconfig.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 — useful if you want the tunnel program to
connect to a non-standard port."

Reading the manual is good.

Attachment: signature.asc
Description: This is a digitally signed message part

Relevant Pages

  • Re: Help! bash annoyingly kills background processes when xterm is closed
    ... > bash, but I'm having a serious usability problem with bash that is ... > Let's say I have an xterm, and in the xterm I have a tcsh running. ... > Now let's say from the tcsh, I fire up an xemacs in the background, ...
    (comp.unix.shell)
  • Re: bash & tcsh
    ... I use bash as the standard shell for all accounts on hp-ux, ... don't use tcsh. ... permissions to match the other system shells. ...
    (comp.sys.hp.hpux)
  • Re: TCSH and me!
    ... tcsh does have some interactive features that bash lacks. ... Spelling correction can be configured to work with file names, ...
    (comp.unix.shell)
  • Re: name completion in terminal?
    ... File completion is built into the c-shell but you have to | turn it on with "set filec". ... Actually, it's built into tcsh. ... Bash and zsh do file completion out of the box. ... Now that bash has the features that tcsh had back when I should probably switch but I still like the logic control syntax of tcsh over bash for scripting ...
    (Fedora)
  • Re: Switching from tcsh to bash as an interactive shell
    ... > For about ten years I've been using tcsh as my command-line shell and bash ... > as my programming shell. ... > the syntax and so have decided to switch to bash for both tasks. ... zsh is the most obvious way to go. ...
    (comp.os.linux.misc)