Parallel and Segmented Downloads No Longer Working
copaceticgeek opened this issue · 7 comments
I recently updated to the newest build. Since then parallel and segmented downloads are no longer working. When using pget-to-local the terminal screen shows the following:
It appears that it only uses one connection now.
It has always been like this for pget-to-local.
1 file is transferred using n amount of parts. There are no parallel transfers with a pget transfer. Only a mirror transfer has parallel and pget.
This can also be demonstrated by opening the .lftp.lftp-pget-status to see the number of parts defined.
For example, when using the defaults.
size=5368709120
0.pos=62750720
0.limit=1073741824
1.pos=1096941568
1.limit=2147483648
2.pos=2173730816
2.limit=3221225472
3.pos=3251339264
3.limit=4294967296
4.pos=4324589568
4.limit=5368709120
I am not sure what the problem is here since what you are claiming is a bug, is actually how it has always behaved for this particular custom command.
Please look here https://lftp.yar.ru/lftp-man.html
Search for -P (case sensitive) or --parallel and you will see this is not a option for the pget command.
Please also check your task manager when using the pget command to see there will a number of ssh/cygwin task equal to the number of parts selected.
Sorry for the confusion and lack of detail in my post. When using the pget command, it is no longer breaking the download into segments. In task manager there is only one instance of ssh/cygwin running. It is also no longer showing the status of the download with the "dots" and "circles" like before either.
When using the mirror command, it is no longer running parallel downloads or segmenting the files.
Try setting the override settings again. I have tested it and cant find any issues.
Thank you. That worked. It is now behaving normally again.
actually, I think I see the problem. i'll fix it now
Ok, so there was a silly bug created by myself. I didn't notice it because of the override worked.
The check to decide if we should use the lftp conf was checking against the wrong filename. That is fixed now so it should work as expected with this fix userdocs/LFTP4WIN-CORE@c593c18
Thanks for letting me know.