On Du, 21 feb 21, 09:20:07, Jeffrey Walton wrote: > On Sun, Feb 21, 2021 at 8:58 AM Reco <recoverym4n@enotuniq.net> wrote: > > On Sun, Feb 21, 2021 at 08:42:45AM -0500, Alan Corey wrote: > > > I guess a question is why you want an RTC. If you have a decent > > > internet connection just run NTP on something and it will set the > > > computer's clock. > > > > IPSec, Tor, sec=krb5* NFS mounts. > > And anything related to X.509. > > In the old days of cell phones, back when you needed a SIM card to get > time from the network, you had to jump through hoops to use a > non-provisioned device for development. > > I think things have gotten better since then. I don't recall seeing > clock problems on unprovisioned devices in a while. > > > At least these four things are badly screwed if Debian OS lacks access > > to RTC. Systemd manages to launch those before NTP-based time > > synchronization kicks in, which leads to funny things to say the least. > > This may be a Systemd bug. I'd say it's up to each daemon to declare its dependencies in the service file. The problems are likely also much less visible for systems that are always on as systemd-timesyncd will quite quickly advance the clock on reboots based on a time stamp saved during shutdown. Kind regard, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Attachment:
signature.asc
Description: PGP signature