the debug build fixed it.
- cracki
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
- cracki
to be precise, ls -l on the server reports "May 30 20:06 11ss-daks-110530.prproj" (GMT+0200) and the remote FTP server seems to report times in GMT ("May 30 18:06 11ss-daks-110530.prproj").
I managed to replicate this on a local FTP server (Gene6 FTP on WinXP) using the same 2 hour timezone offset and a file that has a modification time of 2011-05-30 18:06 (the local server seems to report local times in its "LIST -a").
I managed to replicate this on a local FTP server (Gene6 FTP on WinXP) using the same 2 hour timezone offset and a file that has a modification time of 2011-05-30 18:06 (the local server seems to report local times in its "LIST -a").
- martin
Re: File time reported incorrectly
I have sent you an email with debug version.
- cracki
File time reported incorrectly
this happens on 4.3.3, but not on 4.3.2
this happens on WinXP german and Win7 english.
FTP protocol.
the effect survives a reboot of the computer.
line in "LIST -a" (collected using wireshark, matches ls -l on server):
I am GMT+0200, server is GMT+0200.
connecting using a timezone offset of 2:00 hours, the time is reported as "2011-05-30 19:58". for 1:00, 1:30 and 3:00, the time is reported "correctly".
I suspect "May 30 18:06" and a 2 hour offset are magical values.
this happens on WinXP german and Win7 english.
FTP protocol.
the effect survives a reboot of the computer.
line in "LIST -a" (collected using wireshark, matches ls -l on server):
-rw-rw-r-- 1 crackwitz videoag 612800 May 30 18:06 11ss-daks-110530.prproj
I am GMT+0200, server is GMT+0200.
connecting using a timezone offset of 2:00 hours, the time is reported as "2011-05-30 19:58". for 1:00, 1:30 and 3:00, the time is reported "correctly".
I suspect "May 30 18:06" and a 2 hour offset are magical values.