Your best friend for file transfer.

Fetch application logoFetch

Connection Pacing (3 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 11 years ago by zenroom
  • Latest reply 11 years ago from zenroom
  • zenroom Member

    I use Fetch's "Mirror Folder" to backup and copy large directory trees with many files. When I do this with a slow, older Linux system, I find that the transfer eventually aborts because the Linux system cannot open any more TCP connections, and netstat there will show over 180 connections in TIME_WAIT. It seems that Fetch (4.0.3 on MacOS 10.2.4) is just too fast in this case. I would like to have TCP Connection Pacing as an option, maybe in the form of an N per second maximum limit. Ideally this would be a per shortcut option, since I only need it on a few hosts, but an Obscure Option under Misc would be workable for me. Thanks.

    Posted 11 years ago #

  • Jim Matthews Administrator

    That's a great suggestion -- thanks!

    Jim Matthews
    Fetch Softworks

    Posted 11 years ago #

  • zenroom Member

    One way that I've seen host specific advanced options like this implemented so they're flexible yet not complexicating the basic UI is to have an editable list of the hosts/IP addresses (or even IP address ranges) that the option applies to, with a maximum rate for each. This approach has the mild benefit that once you have recorded this limit for a host, you don't need to recall it each time you make up a new shortcut for that host. It has the downside that the limit isn't recorded in the shortcut, especially if you share shortcuts between fetch installations.

    Posted 11 years ago #

Topic closed

This topic has been closed.