Thanks
- 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
- cracki
Yes, that fixed it. The 1 minute difference is gone. Thanks!
- martin
Re: FTP timezone offset -1 minute for whole hours...
I have sent you an email with link to development version for you to test.
- martin
Re: FTP timezone offset -1 minute for whole hours...
Thanks for your post. This bug has been added to tracker.
- cracki
FTP timezone offset -1 minute for whole hours...
I have files on a linux server box. that box and I are in GMT+0200.
stat on the server reports one file as this:
Modify: 2011-04-20 15:41:10.000000000 +0200
FTP's MLSD on that file says
modify=20110420134110
FTP's LIST reports "13:41"
so those times look okay.
now I connect with winscp, all defaults on 4.3.2. winscp reports "13:41"... winscp either does not know of MLSD/MLST, or winscp doesn't display those (GMT) times in my local time.
the real issue... if I connect and set the 'timezone offset' in 'Environment' to 2 hours 0 mins, that same file is reported as "15:40".
that's not 2:00h, that 1:59h.
an offset of 1:00h is also a minute short. offsets of 1:30h, 2:30h, and 3:00h produce correct results.
weird bug. what's going on?
stat on the server reports one file as this:
Modify: 2011-04-20 15:41:10.000000000 +0200
FTP's MLSD on that file says
modify=20110420134110
FTP's LIST reports "13:41"
so those times look okay.
now I connect with winscp, all defaults on 4.3.2. winscp reports "13:41"... winscp either does not know of MLSD/MLST, or winscp doesn't display those (GMT) times in my local time.
the real issue... if I connect and set the 'timezone offset' in 'Environment' to 2 hours 0 mins, that same file is reported as "15:40".
that's not 2:00h, that 1:59h.
an offset of 1:00h is also a minute short. offsets of 1:30h, 2:30h, and 3:00h produce correct results.
weird bug. what's going on?