Re: bytes missing from server-side copy after copying .sh files
I'm afraid that more users will appreciate the function to be enabled by default than disabled.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- Marko
bytes missing from server-side copy after copying .sh files
Couldn't fit the whole problem on the subject line; I had an issue after transferring a .sh file originally created with makeself on Linux from my desktop to a server.
For (to me, at least) a very nonobvious reason the transfer was cut off 10 bytes short (perhaps because of CRs converted) on the server side. I eventually figured that there's a "text-only" mode transfer (which I assume is similar to FTP's) enabled for certain file types such as .txt and .sh.
The feature obviously is not a bug, but intended behaviour, but since there are .sh files that may contain binary data I'd think a better way would be to either disable that operation by default for .sh files, or at least check inside the .sh file for what kind of data it contains and then decide or ask the user.
The version I was using is 3.8.2 standalone, and if the behaviour has been changed then this rant is largely irrelevant.
For (to me, at least) a very nonobvious reason the transfer was cut off 10 bytes short (perhaps because of CRs converted) on the server side. I eventually figured that there's a "text-only" mode transfer (which I assume is similar to FTP's) enabled for certain file types such as .txt and .sh.
The feature obviously is not a bug, but intended behaviour, but since there are .sh files that may contain binary data I'd think a better way would be to either disable that operation by default for .sh files, or at least check inside the .sh file for what kind of data it contains and then decide or ask the user.
The version I was using is 3.8.2 standalone, and if the behaviour has been changed then this rant is largely irrelevant.