It seems that ssh2 has trouble if input is sent to it too early. ssh1 does not have that problem. Suppose I put the following two lines into an xpostit window and the copy and paste them into an xterm (all in one go -- we're talking about timing problems, remember). ,----- This invokes ssh1 | ssh1 -l root slowfox /bin/sh | echo hello `----- This is what I get with ssh1: ,----- | $ ssh1 -l root slowfox /bin/sh | echo hello | hello `----- One notes that there is a slight pause between the "ssh1" command appearing in the xterm and the "echo hello" line appearing. The third line seems to appear pretty much immediately after the second. So far, so good. rcp.el works fine with ssh1. Now, however, we try the same experiment with ssh2. The following two lines go into an xpostit window and are copyed and pasted into an xterm, all in one go. ,----- This invokes ssh2 | ssh -l root slowfox /bin/sh | echo hello `----- This is what I get with ssh2: ,----- | $ ssh -l root slowfox /bin/sh | echo hello `----- I wait a bit, and then I hit the RET key. This is what I see: ,----- | $ ssh -l root slowfox /bin/sh | echo hello | | hello `----- Apparently, ssh2 seems to have timing problems if input is sent to it too early. If I enter the "ssh -l root slowfox /bin/sh" command, then wait a bit before "echo hello", everything is fine. On my PII/350 FreeBSD box at home, it is sufficient to wait a second or two before the "echo hello". However, on my SPARCstation 4 Solaris box at work, it is necessary to wait more than 10 seconds! Do you observe a similar problem? The ssh versions in question are 1.2.26 and 2.0.12. kai -- Life is hard and then you die.
