Mark Oberfield <oberfiel@...> writes:
> After consulting the Info pages on tramp and reviewing the FAQ I
> cannot determine what is wrong with my configuration of tramp. It
> just seems to hang when attempting to fetch a file remotely.
> I am using tramp v2.0.12.
> ;;; ********************
> ;;; Set TRAMP to use ssh method
> (add-to-list 'load-path "~/.xemacs/xemacs-packages/lisp/tramp/lisp/")
> (require 'tramp)
> (setq tramp-default-method "scp")
> I have configured ssh so that I do not have to provide a password to
> connect to remote machine.
> Viewing the Message Log buffer reveals:
> tramp: Looking for pattern ^.*\(?:Connection \(?:closed\|refused\)\|Host key verification failed\.\|Login \(?:Incorrect\|incorrect\)\|Name or service not known\|Permission denied\.\|Sorry, try again\.\).*\|^.*\(Received signal [0-9]+\).*
> tramp: Looking for pattern Are you sure you want to continue connecting (yes/no)\? *
> tramp: Looking for pattern ^.*\([pP]assword\|passphrase.*\)
> tramp: Looking for pattern .*ogin: *
> tramp: Looking for pattern ^[^#$%>
> ]*[#$%>] *
> tramp: Found remote shell prompt.
> tramp: Initializing remote shell
This is a promising first start. It means that things are not
horribly broken, just badly broken...
> I've set the tramp-debug-buffer to 't
> $ ( test -d /staging/master/build/IFPS12/adapt/ifps/src/unld_to_zns/Makefile 2>/dev/null; echo tramp_exit_status $? )
You should get a *tramp/foo* buffer as well as a *debug tramp/foo*
buffer when you (setq tramp-debug-buffer t). Can you post the
contents of both buffers after trying to access a file?
It is useful to type the complete filename without trying to use
filename completion, so that the *debug tramp/foo* buffer is shorter
and it is easier to spot the problem.
> After this it just pauses for as long as I am willing to wait (several
> minutes). The only way to regain control is to issue a ^G and the
> remote file never gets sucked in.
> My shell on the remote machine is /bin/tcsh and does not require any
> user interaction when logging in. Documentation states that tramp is
> intelligent enough to determine the login shell and Do the Right
> Thing, yet I see very Bourne shell syntax here in the tramp-debug
Tramp sends "exec /bin/sh" to the remote end at the first chance, so
it can assume from them on that it is talking to a Bourne-ish shell.
You can change the /bin/sh part via the tramp-methods parameter
`tramp-remote-sh'. But it must be a Bourne-ish shell, otherwise
Tramp will fail!
A large number of young women don't trust men with beards. (BFBS Radio)