Opened 19 years ago
Last modified 18 years ago
#995 closed Bug report
invalid 'no-transfer' timeout on server
Reported by: | brin_snowdon | Owned by: | Alexander Schuch |
---|---|---|---|
Priority: | normal | Component: | FileZilla Server |
Keywords: | Cc: | brin_snowdon, Alexander Schuch | |
Component version: | Operating system type: | ||
Operating system version: |
Description
'No transfer timeout' is set to the default 120s on
this 0.9.11 Filezilla server, running on W2K, yet it
seems to disconnect clients a lot more quickly - see
examples below for 3 seconds and 4 seconds. Is this
something to do with two users signed in with the same
id? (ratrunner1). I have had to disable 'no transfer
timeout' (i.e. 0) to stop this from happening.
(000110) 07/12/2005 11:04:41 - ratrunner1
(194.62.232.125)> 257 "/" is current directory.
(000110) 07/12/2005 11:04:41 - ratrunner1
(194.62.232.125)> MDTM 3G_FTP_2MB.mp3
(000110) 07/12/2005 11:04:41 - ratrunner1
(194.62.232.125)> 213 20050215180742
(000109) 07/12/2005 11:04:41 - ratrunner1
(194.62.232.126)> PWD
(000109) 07/12/2005 11:04:41 - ratrunner1
(194.62.232.126)> 257 "/" is current directory.
(000109) 07/12/2005 11:04:41 - ratrunner1
(194.62.232.126)> MDTM 3G_FTP_2MB.mp3
(000109) 07/12/2005 11:04:41 - ratrunner1
(194.62.232.126)> 213 20050215180742
(000109) 07/12/2005 11:04:44 - ratrunner1
(194.62.232.126)> 421 No-transfer-time exceeded.
Closing control
(000110) 07/12/2005 11:07:52 - ratrunner1
(194.62.232.125)> 257 "/" is current directory.
(000110) 07/12/2005 11:07:52 - ratrunner1
(194.62.232.125)> MDTM 3G_FTP_2MB.mp3
(000110) 07/12/2005 11:07:52 - ratrunner1
(194.62.232.125)> 213 20050215180742
(000111) 07/12/2005 11:07:52 - ratrunner1
(194.62.232.126)> PWD
(000111) 07/12/2005 11:07:52 - ratrunner1
(194.62.232.126)> 257 "/" is current directory.
(000111) 07/12/2005 11:07:52 - ratrunner1
(194.62.232.126)> MDTM 3G_FTP_2MB.mp3
(000111) 07/12/2005 11:07:52 - ratrunner1
(194.62.232.126)> 213 20050215180742
(000110) 07/12/2005 11:07:56 - ratrunner1
(194.62.232.125)> 421 No-transfer-time exceeded.
Closing control
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Does this still happen with current version of FileZilla Server?