tramp again

[Miles Bader <miles@lsi.nec.co.jp>]

It's been a while since I last tried tramp, so I checked to see if I
could a simple `su' today.  Here's what happened.

First, I tried `/su:localhost:/etc', and tramp told me `you must use a
username with the `su' method'.  This seems wrong -- 99% of the time,
when someone su's they want to su to root; it's annoying enough that
you have to type `localhost', but why should you have to type `root' too?

Okay, anyway, I next tried `/su:root@localhost:/etc'.  Tramp asked me
for a password, and I gave the root password.  Then tramp appeared to
hang, displaying the message:

   Looking for pattern \(Store key in cache\? (y/n)\)\s-*

I guess it was actually looping; here's the *Messages* contents:

   tramp: Opening connection for `root' using `su'...
   tramp: Processing actions
   tramp: Waiting 60s for prompt from remote shell
   tramp: Looking for pattern ^.*\([pP]assword\|passphrase.*\):
   Password: .......
   tramp: Looking for pattern .*ogin: *
   tramp: Looking for pattern ^\(([^) 	]*)\|[^> 	]*[>]\)\s-*
   tramp: Looking for pattern ^.*\(Connection \(?:\(?:clo\|refu\)sed\)\|Host key verification failed\.\|Login \(?:[Ii]ncorrect\)\|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)\?\)\s-*
   tramp: Looking for pattern \(Store key in cache\? (y/n)\)\s-*
   tramp: Looking for pattern ^.*\([pP]assword\|passphrase.*\):
   tramp: Looking for pattern .*ogin: *
   tramp: Looking for pattern ^\(([^) 	]*)\|[^> 	]*[>]\)\s-*
   tramp: Looking for pattern ^.*\(Connection \(?:\(?:clo\|refu\)sed\)\|Host key verification failed\.\|Login \(?:[Ii]ncorrect\)\|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)\?\)\s-*
   tramp: Looking for pattern \(Store key in cache\? (y/n)\)\s-*
   tramp: Looking for pattern ^.*\([pP]assword\|passphrase.*\):
   tramp: Looking for pattern .*ogin: *
   tramp: Looking for pattern ^\(([^) 	]*)\|[^> 	]*[>]\)\s-*
   tramp: Looking for pattern ^.*\(Connection \(?:\(?:clo\|refu\)sed\)\|Host key verification failed\.\|Login \(?:[Ii]ncorrect\)\|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)\?\)\s-*
   tramp: Looking for pattern \(Store key in cache\? (y/n)\)\s-*
   Quit

Here's the contents of the `*tramp/su root@localhost*' buffer:


   mcspd15:~# 

[I indented it; it's actually flush with the left margin]

Has tramp been fixed to not use `shell-prompt-pattern' incorrectly yet?

Maybe that's the problem.

I did (setq shell-prompt-pattern nil) and tried again.  This time, it
hung displaying:

   Waiting 30s for remote `/bin/sh' to come up...

Not sure what was wrong this time; the contents of the `*tramp...'
buffer were the same as before, but *Messages* showed:

   tramp: Opening connection for `root' using `su'...
   tramp: Processing actions
   tramp: Waiting 60s for prompt from remote shell
   tramp: Looking for pattern ^.*\([pP]assword\|passphrase.*\):
   Password: .......
   tramp: Looking for pattern .*ogin: *
   tramp: Looking for pattern nil
   tramp: Found remote shell prompt.
   tramp: Waiting 30s for remote `/bin/sh' to come up...
   Quit

Does tramp seem this fragile for anyone else?

-Miles
-- 
I'd rather be consing.