On 04/24/2012 08:36 AM, David C. Rankin wrote: > This would explain why sftp got 'stuck' waiting on select() as Tim found! > Somewhere in the sftp code, it must be checking on the ssh output beginning with > line '6' looking for IP and port information: > > debug1: Connecting to nirvana [192.168.6.17] port 6660. > > however, with 5.9 it is getting: > > debug1: Connection established. > > Causing the code to endlessly wait on select() to get the IP and port!! Now - > how to find where this takes place in the code to confirm?? It is probably a > hardcoded as some array index like 'sshOutputLine' which will now need to be > changed to 'sshOutputLine' to account for the deleted line in the output, or > just rewritten with a regex to look for "[www.xxx.yyy.zzz] port 01234" in the > output. > > How do we look for code like this to rule in or rule out this problem? I think the CHANGELOG narrows down the search and it is what was identified earlier: 2-19-2002 - get() now emits mimetype, fixes problem with konqi not downloading file for viewing in kpart. - get port number using getservbyname instead of hard coding it. So it is the 'getservbyname' call that is relied upon to get the port information -- and I'll bet the fix is just what we talked about above. Now how to figure out how to make the pieces of 'getservbyname' return the port correctly again from the ssh output? -- David C. Rankin, J.D.,P.E.