I do agree with you, and I do the same on any system which has a battery-backed RTC and a persistent network connexion (taking care also of timezone issues)...

However, I'm afraid that after a module reboot it may take a few seconds to retrieve a correct time.

Also, when running without GPS, without network and without modem (which seems a supported, even if unusual, configuration), it seems that I'll never have a correct time at all.

In both cases, the module will always start with Unix epoch (1970-01-01-00:00:00) for at least a few seconds, and so risk the risk to overwrite log files do exist (as the log starts as soon as possible).

Of course, I'm running in that configuration (no modem, very often without Wifi, GPS not always having time) otherwise it would not be fun... :-(

So that's why I wanted to be independent of time.

But it would not be complex to support both syntaxes, to offer this choice.

Ludovic

Le 09/11/2022 à 22:57, Craig Leres a écrit :

On 11/9/22 13:52, Ludovic LANGE wrote:

Naming would be 'automatic' with something like :
`/sd/log/<vehicleid>/<#power on>/<log prefix>/<#rotations>.<log extension>`

When I auto-name log or trace files I like to use the date and time. This format sorts nicely and makes it easy to find the file that contains the date+time of interest. So I would counter-propose:

YYYY-MM-DD-HH:MM:SS.<log extension>

Craig