Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #5073


Ignore:
Timestamp:
Jul 29, 2010 12:42:55 PM (8 years ago)
Author:
dkocher
Comment:

The timeout settings are not read from .ssh/config but can be set in the Connection Preferences. However, there must be an issue with stalled SSH connections as noted previously in #3941 and #4214.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5073 – Description

    initial v1  
    11I've noticed recently (after upgrading to the latest version and also in 3.4.2 - I had been using an old old one 3.1 I think...), that if I leave an SFTP window open for a period of time (I would guess about an hour), and then I try to perform any action, Cyberduck will show the "spinner" at the bottom of the window, but nothing happens. Not even a time out.
    22
    3 I have the following in my ~/.ssh/config file - which used to be enough to stop this problem:
     3I have the following in my `~/.ssh/config` file - which used to be enough to stop this problem:
    44
     5{{{
    56ServerAliveInterval 120
    67ServerAliveCountMax 10
    78TCPKeepAlive yes
     9}}}
    810
    911Do newer version of CyberDuck ignore what is present in this file? I've tried version combinations of the commands in the file, and also have a file named ~/.ssh/ssh_config (which some sites suggest it should be), but to no avail.
swiss made software