Differences
This shows you the differences between the selected revisions of the page.
2012-05-07 | 2013-04-11 | ||
getting rid of ui_transfer_custom (martin) | ui_login_environment#dst (martin) | ||
Line 6: | Line 6: | ||
There are several factors that affect conversion and interpretation of the timestamps: | There are several factors that affect conversion and interpretation of the timestamps: | ||
^ Factor ^ Symptom ^ | ^ Factor ^ Symptom ^ | ||
- | | [[ui_login_environment#daylight_saving_time|Daylight saving time (DST)]] | Timestamps of some files are shifted by one hour. | | + | | [[ui_login_environment#dst|Daylight saving time (DST)]] | Timestamps of some files are shifted by one hour. | |
| [[ui_login_environment#timezone_offset|Server timezone offset]] | Timestamps of all files are shifted by the same time span. [[SCP]] and [[FTP]] protocols are affected. | | | [[ui_login_environment#timezone_offset|Server timezone offset]] | Timestamps of all files are shifted by the same time span. [[SCP]] and [[FTP]] protocols are affected. | | ||
| Local file system is FAT | File timestamp is always rounded to the next even second. This is a limitation of the legacy FAT filesystem. For this reason WinSCP ignores less than 2-seconds time difference with all its [[task_synchronize|synchronization]] features. Although FAT is an old filesystem, it remains in common use today on flash based storage media and devices (such as USB flash drives, camera cards, phone internal storage, portable audio players etc). Standard ZIP archive files also use a similar timestamp system internally, so unzipped files will behave as if they have been copied from a FAT filesystem. | | | Local file system is FAT | File timestamp is always rounded to the next even second. This is a limitation of the legacy FAT filesystem. For this reason WinSCP ignores less than 2-seconds time difference with all its [[task_synchronize|synchronization]] features. Although FAT is an old filesystem, it remains in common use today on flash based storage media and devices (such as USB flash drives, camera cards, phone internal storage, portable audio players etc). Standard ZIP archive files also use a similar timestamp system internally, so unzipped files will behave as if they have been copied from a FAT filesystem. | | ||
Line 15: | Line 15: | ||
===== [[windows]] Windows vs. Unix ===== | ===== [[windows]] Windows vs. Unix ===== | ||
- | For certain reasons certain versions of Microsoft Windows (NT, 2000, XP, 2003 and Vista)((Basically all NT-class versions of Windows until Windows Vista. The timestamp shifting was removed since Window 7.)) shifts timestamps of ALL files by one hour once Daylight Saving Time starts and/or finishes((See article [[http://www.codeproject.com/datetime/dstbugs.asp|Beating the Daylight Savings Time bug]])). For example, for file created on 2005-02-25 14:00, Windows applications (like Windows Explorer or WinSCP) will show modification time 2005-02-25 15:00, when DST is in effect. Unfortunately, to allow [[task_synchronize|synchronization]] functions to work, WinSCP has to apply the same correction to timestamps of remote files as Windows apply to timestamps of local files. As the remote operating system, being typically Unix-style, usually does not perform the Windows NT-style correction, you will see by default different timestamps in directory listing of WinSCP, than you see in directory listing on the server (for example in ''ls'' listing). You can change this in [[ui_login_environment#daylight_saving_time|session options]], but that will render synchronization non-functional. | + | For certain reasons certain versions of Microsoft Windows (NT, 2000, XP, 2003 and Vista)((Basically all NT-class versions of Windows until Windows Vista. The timestamp shifting was removed since Window 7.)) shifts timestamps of ALL files by one hour once Daylight Saving Time starts and/or finishes((See article [[http://www.codeproject.com/datetime/dstbugs.asp|Beating the Daylight Savings Time bug]])). For example, for file created on 2005-02-25 14:00, Windows applications (like Windows Explorer or WinSCP) will show modification time 2005-02-25 15:00, when DST is in effect. Unfortunately, to allow [[task_synchronize|synchronization]] functions to work, WinSCP has to apply the same correction to timestamps of remote files as Windows apply to timestamps of local files. As the remote operating system, being typically Unix-style, usually does not perform the Windows NT-style correction, you will see by default different timestamps in directory listing of WinSCP, than you see in directory listing on the server (for example in ''ls'' listing). You can change this in [[ui_login_environment#dst|session options]], but that will render synchronization non-functional. |
===== Synchronization ===== | ===== Synchronization ===== | ||
If you happen to have the same files locally and remotely with the different timestamps, you can update them without transferring the files again. Use function //Synchronize// in //[[task_synchronize_full#synchronization_mode|Synchronize timestamps]]// mode. | If you happen to have the same files locally and remotely with the different timestamps, you can update them without transferring the files again. Use function //Synchronize// in //[[task_synchronize_full#synchronization_mode|Synchronize timestamps]]// mode. |