Not sure if this fits in cPanel forums, but maybe somebody can at least try and provide some workaround to this.
We're using Pure-FTPD and over the last 2 years, we noticed a very frustrating behavior. In FileZilla client, whenever somebody uploads a (big) file, the upload immediately gets renamed to some serial number (e.g.: .pureftpd-upload.4bca436d.15.2455.1bb2fab2) but it frequently happens that mid-way thru the upload, the client's IP address changes. What happens next is one of the 2 things:
1) The file gets re-uploaded from scratch.
2) The file upload resumes.
More often than not, scenario #1 happens. If the client refreshes the directory in FileZilla client, it seems like the serial-named file (e.g.: .pureftpd-upload.4bca436d.15.2455.1bb2fab2) gets erased or an attempt to rename it back to the normal file name fails and the file gets deleted!
This is becoming a very aggravating issue because some dump files are as big as 4GB and on sh*tty internet access such as 800kbps upload, this takes 1.5 day! Imagine this happening twice for the same file and now it takes 3 days to finish the upload (if the IP address does not change again, which it does on ASDL connections almost every day) !
Anything that can be done to stop this from happening? (inb4 set a cron job in cPanel to make a copy of the .pureftpd-upload.* files every hour)
Would it work better under Pro-FTPD ?
We're using Pure-FTPD and over the last 2 years, we noticed a very frustrating behavior. In FileZilla client, whenever somebody uploads a (big) file, the upload immediately gets renamed to some serial number (e.g.: .pureftpd-upload.4bca436d.15.2455.1bb2fab2) but it frequently happens that mid-way thru the upload, the client's IP address changes. What happens next is one of the 2 things:
1) The file gets re-uploaded from scratch.
2) The file upload resumes.
More often than not, scenario #1 happens. If the client refreshes the directory in FileZilla client, it seems like the serial-named file (e.g.: .pureftpd-upload.4bca436d.15.2455.1bb2fab2) gets erased or an attempt to rename it back to the normal file name fails and the file gets deleted!
This is becoming a very aggravating issue because some dump files are as big as 4GB and on sh*tty internet access such as 800kbps upload, this takes 1.5 day! Imagine this happening twice for the same file and now it takes 3 days to finish the upload (if the IP address does not change again, which it does on ASDL connections almost every day) !
Anything that can be done to stop this from happening? (inb4 set a cron job in cPanel to make a copy of the .pureftpd-upload.* files every hour)
Would it work better under Pro-FTPD ?