![]() ![]() the directory tree scanned) while the download is ongoing, so in case of huge directories, if the download is interrupted and resumed, maybe the scanning of the directory is not resumed properly. And if you download a folder, you must have 100% guarantee that all its contents get added to the queue. ![]() If a queue becomes empty and you haven't explicitely deleted anything from it, you must be 100% sure that everything in it has been downloaded. I don't know whether the missing directories have never got into the queue (I'm ALMOST sure this was the case) or if they did and then they failed to download, but in both cases SILENTLY failing to download is a disaster. Then I found out that more than half of the directory tree simply HADN'T BEEN DOWNLOADED. I never, ever deleted anything from the queue nor did I ever receive any error prompt to which I could have given the wrong answer.Īfter hours of downloading, the queue was finally empty and FileZilla was apparently done downloading. I right-clicked on a directory (that contained a lot of subdirectories with thousands of files) on the server and selected "download".ĭuring the download process I lost connection a few times and sometimes had to restart filezilla (because of another bug, that sometimes you can't resume processing a queue until you restart filezilla), but then I always resumed that shouldn't be a problem at all. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |