Is it checked whether systemd-timedatectl is running or available before executing dietpi-update?
If so, what is the background?
I get a fright every time I get a “Retry”, but with exit and re-execution everything is fine.
In this specific case, systemd-timedatectl is actually not present.
If the service is only inactive, there are no problems.
I’m asking because I use chrony for time synchronization and also have an RTC installed in the Pi’s or is already present in the Pi 5.
Simply disable time sync in dietpi-config
Where should I do that?
Under dietpi-config → 8. Network Options: Misc I can’t find a real option to do this, but maybe I can’t see the wood for the trees.
Nevertheless, if the service is still available but inactive, then I have no problem, but if it is no longer available, then dietpi-update complains.
Once again, please let me know!
Thanks
Meant was the “custom” option if you use a dedicated time sync daemon (chrony), to prevent DietPi from running systemd-timesyncd on updates etc. It does not use systemd-timedatectl btw, which is a CLI frontend, but systemd-timesyncd only.
1 Like
dietpi-config > 4 : Advanced Options > Time sync mode > 0 : Custom
1 Like
Sorry for the wrong choice of words, I only had it halfway in my head. 
I had already made this selection based on the RTC.
I wanted to reproduce it on other systems, but “my effect” has not yet reappeared.
If it occurs again, I will post it.
Thanks for the clarification.