Make LOG filenames more readable [REQUEST]

Discuss new features and functions
Posts: 65
Joined: 8 Jun 2023

Synchronizator

I would like to suggest changing how the filenames of LOG files available at

C:\Users\YOUR-USER-NAME\AppData\Roaming\FreeFileSync\Logs

are named. Instead of e.g.
SyncSettings 2023-06-13 142359.331.log
let FreeFileSync and RealTimeSync create
SyncSettings 2023-06-13 14_23_59.331.log
Or even better
SyncSettings 2023-06-13 14.23.59_331.log
or [the best in my opinion]
SyncSettings 2023-06-13 14.23.59 331.log
or eventually
SyncSettings 2023-06-13 14_23_59 331.log

And by the way: what is that last 3-digit number? A checksum of some sort?
Posts: 1037
Joined: 8 May 2006

therube

Milliseconds, time_format.
Posts: 65
Joined: 8 Jun 2023

Synchronizator

Well then, my suggestion would be to start writing them as [in this example]
SyncSettings 2023-06-13 14_23_59_331.log
or
SyncSettings 2023-06-13 14.23.59.331.log
User avatar
Posts: 4056
Joined: 11 Jun 2019

xCSxXenon

Here's an important question I think:
Why does it matter?
Posts: 65
Joined: 8 Jun 2023

Synchronizator

[...]
Why does it matter? xCSxXenon, 13 Jun 2023, 17:45
To make them more readable at a glance

Have you seen how ~50 LOG files created within one hour look like in that folder? I have

Have you tried using LOG files to pin point some change of items after making some stupid mistake? I have
User avatar
Posts: 4056
Joined: 11 Jun 2019

xCSxXenon

Ah yes! I could see a mash of run-on numbers being tough to sort through