Suppose I do this: lftp> get -c "ftp://host.somewhere.com/the/path/to/the/file/huge_file.iso & lftp> get -c "ftp://host.nowhere.com/a/path/to/the/copy/huge_file.iso & lftp> get -c "ftp://host.elsewhere.com/the/path/huge_file.iso & lftp> get -c "ftp://host.here.com/the/path/to/the/file/huge_file.iso & Well that's lots of attempts to different hosts trying to get the same file. If all the hosts are overloaded it works more or less, I can kill off the other three when the first succeeds. But it would be nice if lftp could check to see if the local file is being fetched already and block another get. Also if one of the host completes the file all the others immediatly complete too. BTW This should especially apply if I use -o to _make_ the file names the same. Of course the other interpretation is for a multi-site pget ... Perhaps a 'net:overall-connection-limit' to tell lftp which is wanted or maybe that's too evil :-) On a related note there's an interpretation issue for "connection-limit". Suppose there are two gets to the same site and connection-limit is one, neither can get a session so they take turns hitting the site. But as there is only one connection allowed to the site shouldn't they have the same connection even at that time; so if set net:reconnect-interval-base 10 set net:reconnect-interval-max 10 set net:reconnect-interval-multiplier 1 the site gets hit once every 10 seconds not twice every 10 seconds. I don't think this should also apply to the overall-connection-limit, not often anyway. -- Rob. (Robert de Bath <http://poboxes.com/rdebath>) <rdebath @ poboxes.com> <http://www.cix.co.uk/~mayday>
