Implement time-sync.target

Extract from systemd.special

<quote>
time-sync.target

Services responsible for synchronizing the system clock from a remote source (such as NTP client implementations) should pull in this target and order themselves before it. All services where correct time is essential should be ordered after this unit, but not pull it in. systemd automatically adds dependencies of type After= for this target unit to all SysV init script service units with an LSB header referring to the "$time" facility.
</quote>

LE currently has Kodi depend on network-online.target, but there can be a variable delay before the clock is sync'd. Implementing time-sync.target and having Kodi depend on it would would avoid problems with e.g. mounting network shares.

Quote from chewitt

Correct time is a good thing but is also cosmetic to the Kodi GUI so there is no reason to make Kodi start depend upon it. From a support perspective this would make things worse given that some routers act as bad/misconfigured NTP servers, users have a habit of adding typos to their input, and some ISP's blocking port 123 (lord knows why, but it happens).

As 99% of NTP issues are seen on Raspberry Pi .. the cure is adding an RTC card not adding workarounds to the OS.

Hmmm. It may be 'cosmetic' to you...but if Kodi starts before the clock is in sync, my network mounts fail.
Interestingly, OSMC doesn't exhibit the problem - only difference being that I do the network mounts via /etc/fstab, rather than systemd [although I understand systemd handles fstab under the covers].
Perhaps make it possible to configure whether Kodi uses time-sync.target or does what it currently does?
This would mean actually implementing time-sync.target though, which you appear reluctant to support.

PS I am aware there are workarounds for the mount failures. I have to use them :-}
PPS I don't think my proposal is a workaround, rather a solution...
[hr]
chewitt
I just reread my last reply, I wasn't being snarky, honest :-}
[hr]
Since LE already has an option "wait for network" in the LibreELEC settings add-on, perhaps
another option "wait for clock synchronised" could be added, so people who don't care
about the functionality needn't specify it.

Do I take it that nothing is going to happen about this proposal?

Quote from Grimson

Get one of these Mini RTC Module for Raspberry Pi – The Pi Hut and your problem is solved.

Thanks, I may well do that - shame they've sold out!

Quote from Jocke.Sve

Approx 1$:
Buy Products Online from China Wholesalers at Aliexpress.com

Thanks. My German is near non-existent, but it seems the lead time is 30-50 days.
I'll try the PiHut in a week or so :-}

Quote from Jocke.Sve

German? AliExpress?

Yep. I tried the UK flag, maybe I should try the US flag.
Anyway, no big deal.

I think we can safely draw a line under this discussion.
I ended up getting one of these HALJIA DS3231 Precision RTC Clock Module Memory Module: Amazon.co.uk: Electronics
and plugging it in.
Add
dtoverlay=i2c-rtc,ds3231
to config.txt and bingo!