Custom Query (8117 matches)
Results (415 - 417 of 8117)
|#420||No Keep Alive in SFTP over SSH2|
The keep alive function does not appear to work when using SFTP over SSH2 mode. Most FTP servers kick you off when the connection goes idle, so implimenting this feature to work under SSH2 would be a great addition. I'm sure many of us with remote servers would like to keep an open FTP session in the systray while working on their sites.
|#421||I got the reason that cannot disply file list.|
The reason is date-time format. Filezilla cannot parsing local date-time format that include 2byte character.
Below is reasult excute 'ls -la'
drwxr-xr-x 27 root root 1024 7Ô 5| 19:18 . drwxr-xr-x 27 root root 1024 7Ô 5| 19:18 .. -rw------- 1 root other 73 7Ô 5| 19:18 .TTauthority -rw------- 1 root other 98 7Ô 5| 19:18 .Xauthority -rw-r--r-- 1 root other 548 7Ô 5| 19:08 .cshrc -rw-r--r-- 1 root other 548 7Ô 5| 17:35 .cshrc.old -rw-r--r-- 1 root other 124 7Ô 5| 17:34 .cshrc.org drwxr-xr-x 12 root other 512 7Ô 5| 19:18 .dt -rwxr-xr-x 1 root other 5111 5Ô 17| 11:37 .dtprofile . . .
|#422||File size difference in transfer|
I transfered a install.sh file to a UNIX server and it was adding byte size to (832 bytes) the file, causing it to not to run by command line request. I transfered it to another server where the file ran fine and the size was correct (802 bytes). Each time I had Admin rights and I transfered the file as ASCII mode. The transfer was SSH secure each time. I was following a migration task and had to get the developer of the code to witness the issue before we discovered what the problem was preventing the file from running as developed. FYI - the .sh file called a tar.gz file to execute and install inhouse software on the server. We had to use another FTP application to accomplish our migration process.