Pete Forman <[EMAIL PROTECTED]> writes:
> Wrong number of arguments: format, 0, "Couldn't find remote `%s' prompt."
> Starting remote shell `/bin/ksh' for tilde expansion...
>
> (The first indicates a minor bug in the error message code.)
Thanks, I fixed it.
> The debug buffer is
>
> # Opening connection for gsez020@omen using rcp...
> # Waiting 60s for shell or passwd prompt from omen
> IRIX Release 6.5 IP30 omen
> Copyright 1987-1999 Silicon Graphics, Inc. All Rights Reserved.
> Last login: Tue May 16 15:44:12 BST 2000 by [EMAIL PROTECTED]
> omen$ # Initializing remote shell
> $ exec /bin/sh
> # Waiting 30s for remote `/bin/sh' to come up...
> exec /bin/sh
> omen$ # Setting up remote shell environment
> exec /bin/sh
> omen$ s# Trying `stty -onlcr'
> exec /bin/sh
> omen$ stty -echo# Waiting 30s for `set +o history'
>
> stty omen$ # Waiting 30s for `unset MAIL MAILCHECK MAILPATH'
> omen$ $ PS1='
> /////
> '; PS2=''; PS3=''
> # Waiting for remote `/bin/sh' to come up...
> /bin/sh: history: bad option(s)
> # Waiting for remote `/bin/sh' to come up...done
> $ echo ~root
> ~root
> # Looking for remote executable `/bin/ksh'
> $ test -x /bin/ksh ; echo $?
> 0
> # Found remote executable `/bin/ksh'
> # Starting remote shell `/bin/ksh' for tilde expansion...
> $ exec /bin/ksh
This does not look like the rcp.el is waiting for the remote shell
prompt to appear from `exec /bin/sh'! Look where it says `$ exec
/bin/sh' and where it then displays the $ prompt.
And why does it say `exec /bin/sh' so often?
Hm.
kai
--
Beware of flying birch trees.
