Mremoteng: Time for Backup File differed 2 houres to MEZ

Created on 7 Apr 2017  路  2Comments  路  Source: mRemoteNG/mRemoteNG

Closing the mRemoteNG saves a Backup File like
Filename.xml.20170407-1135075365.backup.
The Time 1135 differed from the save time 2 houres.
I closed mRemoteNG at 1335.


|||
|--:|---|
|Operating system | Windows 7 x64 |
|mRemoteNG version| 1.75 aplha 3 |
|mRemoteNG version| Prerelease v1.75.7003 (Hotfix 4) |

Bug
Source
picture peter-franken
👍1

Most helpful comment

resolved in commit 6dcef71

The backup code was using using UTC in the backup name. I've changed this to use local system time.

picture sparerd on 11 May 2017
🎉1 👍1

All 2 comments

resolved in commit 6dcef71

The backup code was using using UTC in the backup name. I've changed this to use local system time.

sparerd picture sparerd on 11 May 2017
🎉1 👍1

The reason this was using UTC is to ensure that the most recent backup is always the highest numbered. Using local time could cause this to not be the case if the time zone is changed, daylight savings time changes effect, or if multiple users in different time zones access the configuration file (some users share their configuration files on a server). I would recommend reverting this change.

rmcardle picture rmcardle on 9 Dec 2017
Was this page helpful?
0 / 5 - 0 ratings

Related issues

jelbo picture jelbo  路  4Comments
LIyoai picture LIyoai  路  4Comments
sparerd picture sparerd  路  3Comments
luke-weller picture luke-weller  路  4Comments
PCNerd2001 picture PCNerd2001  路  3Comments