![]() So the FAT32 one is modified last.įair enough, but in all circumstances, whatever I do, the 8:52 is taken as newer. ![]() The other is on FAT32 and is modified at 8:52. My time is UTC 2 (DST 1) and I create two files. Let me test this.įrom testing it is clear that these are exact 1-hour intervals, not something half-way. Because if when I specify 1 hour ignore, it is then going to always ignore anything SMALLER than 1 hour (which would be pointless for daylight savings differences) there will be a lot of annoyance if the program can no longer identify which file was most recently changed. * Does FFS use the full-hour differences as that (multiples of hours) or as maxima (as you specify). Timestamp difference constitutes a sync-conflict. Of unequal size and a timestamp difference smaller than the specified maximum I suppose (no personal experience) that equally named files at either end Smaller than the maximum timestamp difference will then be considered as "equal" See the FFS help.Įqually named files at either end of equal size and a timestamp difference To a value higher than your maximum time-zone changes. If that is not an option, you might consider setting the FFS maximum timestamp difference If possible, try switching the file system of your storage media to a UTC timestamp based one. You can expect full-resync problems when changing time-zones. Time-setting (like the still quite often used FAT16/32, particularly for USB sticks), ),Ĭonversely, if you use a file system in which the timestamp depends on the local If you use a file system that saves the timestamp in UTC (NTFS, EXT2/3/4/.
0 Comments
Leave a Reply. |