Custom Query (8073 matches)


Show under each result:

Results (157 - 159 of 8073)

Ticket Resolution Summary Owner Reporter
#967 logging screen win nt Alexander Schuch seb_sc


on Windows NT 4.0 i can't see correctly the log in the filezilla server interface. The whole Logging Line are display on the same line.

I have try several version of filezilla server ( also the latest ) and i have the pb. I have also try this on several pc always under win nt 4.

#968 Filezilla resumes while OVERWRITE is selected Alexander Schuch largo1

Sometimes the client tries to resume instead of overwrite the destination (my pc). That produces an error "data is invalid" or produces a larger than the original file.

#971 Filezilla Hangs in SFTP+ClientAliveInterval Alexander Schuch seelie

SFTP using SSH2 works fine with the default (server-side) sshd_config setting, "ClientAliveInterval 0"

However, Filezilla is stuck in this infinite loop: "SftpControlSocket.cpp(2423): ResetOperation(1)" "SftpControlSocket.cpp(2596): OnReceive(0)" "SftpControlSocket.cpp(2596): OnReceive(0)" "SftpControlSocket.cpp(2596): OnReceive(0)" ... causing 100% CPU load, if you set: "ClientAliveInterval 15 (or any non-zero value)" --i.e. if sshd sends a message through the encrypted channel to request a response from the client--, and when (ClientAliveInterval * ClientAliveCountMax) seconds have passed.

Always reproducible on FileZilla 2.2.17 on my Windows 2000 Pro SP4.

This problem happens both for "KeepAlive yes/no" in sshd_config, but in my test, Filezilla does: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) many times when KeepAlive no, while doing it only once when KeepAlive yes. (This pert may be unrelated to the above problem.)

debug.log ("Trace messages from the FTP engine") attached. This log was taken when sshd_config was: KeepAlive no ClientAliveInterval 15 ClientAliveCountMax 3 And the problem seems to have happened 45 seconds after the session becomes idle.

Quote from man sshd_config --- If ClientAliveInterval (above) is set to 15, and ClientAliveCountMax is left at the default, unresponsive ssh clients will be disconnected after approximately 45 seconds. ---

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.