24 Apr
2012
24 Apr
'12
midnight
On 04/23/2012 03:26 PM, David C. Rankin wrote:
I would have expected ssh to read this on its own, but now that you
mention it I do remember a port 22 parameter being passed to ssh when
invoked by the sftp kioslave. I would look in ksshprocess.cpp and see if
the sftp kioslave was hardcoded to port 22 for some reason.
Tim
On 04/23/2012 02:44 AM, Timothy Pearson wrote:
Tim,
I built tdelibs and tdebase and tested sftp. There is GOOD news and BAD
news.
The good new - I can connect with sftp!! The bad news - the kio is not
reading
host/port information from ~/.ssh/config. This requires that you manually
specify a port (if not 22) where sftp:// used to read this information
from the
HOST/PORT information contained in ~/.ssh/config. Eg:
Host arete.3111skyline.com arete
Port 6629
Host fax.rlfpllc.com fax
Port 6631
I don't know what reads this file, but it is read currently when fish://
is
invoked and it was previously read by sftp:// before this bug appeared.
Any idea
where this occurs? Fixed (hacked around) in GIT hash e72f492.
Basically select() no
longer
works on newer systems (could be due to a malfunction of some kind, but
it
doesn't really matter), so instead of busywaiting on select(), newer
systems will busywait on read().
Tim
WOHOO!!! Will test and report back. Sorry, I've been swamped the past
couple of
days. I'll definitely try and build/test tonight!