I develop WordShell (http://wordshell.net), which allows users to manage multiple WordPress sites at once. On the back-end, it prefers to use lftp if it can.
As much parallelism as possible for speed is a good thing (when doing a 'mirror' operation, whether to back up the site, or update to a new version of something).
However, there's no easy way to detect how many logins a remote site might be able to support at once. So it falls to the user to experiment, and then add the configuration options to record the results. The right result might be wrong later if the server administrator reconfigures his FTP server.
It would be great if lftp was able to handle this for me. So, instead of "mirror --parallel=15" or some other guess, you'd do "mirror --parallel=3 --increaseparallel", and then lftp would start from a conservative 3 parallel logins, but keep trying to ramp up from there according to some algorithm until it hit a login error. It'd have to assume that login error was due to excessive parallelism, in the absence of an infallible method. (Of course the problem might be something else - the server might limit logins due to load, or total logins from *all* users, etc.).
What do you think? Best wishes, David -- WordShell - WordPress fast from the CLI - www.wordshell.net _______________________________________________ lftp-devel mailing list lftp-devel@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp-devel
