3.7.6 (Build 306) Changed time ahead by 1 hour

Using 3.7.6 (Build 306) on Windows 2000 SP4.

The Changed time displayed is 1 hour ahead (it shows 10:18:38 PM instead of the correct 9:18:38 PM)

3.7.5 (Build 254) running at the same time shows the correct time 9:18:38 PM

Please refer to change log:

Unix-style approach to Daylight saving time (client does adjustment) is made default. This can affect interpretation of timestamps of your files. Use function Synchronize with option Synchronize timestamps only, not files to resolve it.

Using Synchronize with Synchronize option "Synchronize timestamps only, not files" does not change the Changed time of my files (still ahead one hour).

I notice that this Synchronize option does not "stick" (stayes checked). If I go into Synchronize again (after I set the option and click on "OK"), this option is unchecked again and "Delete files" is checked.

The Synchronize options "sticks" (stayes checked) after checking "Use same options next time".

However this does not change the 1 hour ahead of my Changed files display.

On my servers I connect to, I have FreeBSD 5.4, FreeBSD 4.10 and OpenBSD 3.7 running. All three give the wrong time.

mr wrote:

Using Synchronize with Synchronize option "Synchronize timestamps only, not files" does not change the Changed time of my files (still ahead one hour).

Please tell me, step by step, what you are doing.

Using my Windows 2000 SP4 workstation, I connect with WinSCP 3.7.6 (Build 306) to my servers running FreeBSD 5.4, 4.10 and OpenBSD 3.7.
I connect to the servers /var/log directories, using Explorer view and I can see all the server log files displayed.

The timestamp of the individual files as seen in the column labeled "Changed", is ahead by one hour (into the future).

Per your recommendation I then change the Synchronize settings:

Synchronize > Local directory : C:\Temp\
Synchronize > Remote directory > /var/log
Synchronize > Direction/Target directory > Remote > Checked
Synchronize > Synchronize options > Synchronize timestamps only, not files
Synchronize > Synchronize options > Selected files only > Not checked
Synchronize > Synchronize options > Compare criterions > Modification time > Checked and grayed out
Synchronize > Synchronize options > Same size only > Not checked
Synchronize > Transfer settings > Default transfer settings
Synchronize > Use same options next time > checked once, now not checked


I click on the "OK" button and the Synchronization windows disappears.

I click on refresh, the Explorer view gets updated and the timestamp of the files is still one hour ahead.


I am in The EST time zone and of course we are on daylight saving time now, which may explain the one hour ahead.

But perhaps WinSCP cannot read the daylight saving status of FreeBSD 's ?
Could you make this new Unix-style approach to Daylight saving time (client does adjustment) optional?

mr wrote:

I click on the "OK" button and the Synchronization windows disappears.

The timetamp synchronization should start then. Well maybe its too quick to be even noticed, but I doubt it. Can you post a log file?

But perhaps WinSCP cannot read the daylight saving status of FreeBSD 's ?

WinSCP does not care about it. Timestamps are sent in UTC format, which is unaffected by the DST. Maybe your server fails to adjust it.

Could you make this new Unix-style approach to Daylight saving time (client does adjustment) optional?

It is optional. Just select "Server adjusts DST". However it is against the SFTP specification.

Great, your input solves the puzzle.

1. The clocks of my servers are NOT set to UTC, but to local time.

2. The setting:
WinSCP Login > Environment> Daylight saving time > Server adjusts DST

instead of the default:
WinSCP Login > Environment> Daylight saving time > Sever works in UTC time (adjust DST locally)

works and my files have now the correct timestamp.

Thanks for this excellent software.

Does not help in my case: whatever the login environment DST setting, WinSCP timestamp is 1 hour ahead of what ls reports.
(I just made the same comment on another thread, sorry for double posting)

Hi,

setting the Daylight Saving Time to "Server adjusts DST" works for me. Unfortunately, whenever I import sessions from PuTTY, this option gets set to "Server works in UTC time".

It's not a problem. Just a hassle. I'll "just" have to load each session, click on Environment, change the option, click on save, accept the name, accept the fact it's already there, and I'm done. Until the next import... Unfortunately that has to happen quite often, and for about 40 sessions. *sigh* I was working with the winscp.ini, which has been problematic for some time now and seems to be neglected from further development (probably because I'm one of the very few using it).

As I said: No problem, just uncomfortable. Just wanted to mention it; maybe a new version could look into that.

Even with having to change each and every session winscp is one of *the* most important tools (PuTTY, Pageant) for me. Thank you, Martin.

maelcum wrote:

setting the Daylight Saving Time to "Server adjusts DST" works for me. Unfortunately, whenever I import sessions from PuTTY, this option gets set to "Server works in UTC time".

Make it default session setting. It should help. I hope :-)