Opened 14 years ago
Closed 14 years ago
#4171 closed Bug report (rejected)
Time change on local machine not recognised by client
|Reported by:||vfrrider||Owned by:|
|Component version:||Operating system type:||Windows|
|Operating system version:||XP SP2|
If after starting Filezilla, you change the date and time on the workstation, the displayed timestamps of the files on the server are adjusted by the same amount.
To repeat error.
Set time on workstation incorrectly by a large amount backwards ie 6 months
Connect to server
Correct time on workstations
Timestamps on server files are now displayed as being 6 months in future.
Restarting Filezilla shows correct timestamps
I know that the local machine time should always be correct, but in this instance it was not when Filezilla was started.
Change History (1)
comment:1 by , 14 years ago
|Status:||new → closed|
Note: See TracTickets for help on using tickets.
Things like this are expected if you tamper with the system's clock. Time should always be continuous and uniform.
Either your computer is decades old or you have very broken hardware, otherwise a normal clock skew cannot accumulate to 6 months.
You want to use a proper NTP client to keep your clock synchronized.