ntpd?

[undeterminant]

Running systemd-analyze blame on my RPi, I realize that openntpd is the slowest process to start (almost twice mysqld), while the regular ntpd is very fast on my laptop which runs the x86_64 version of Arch.

Is there any reason why the regular ntpd isn't provided in the repositories? Right now, it's not there.

Also, I apologise if this is the wrong forum, but it seems like this would be the best place to put this.

[WarheadsSE]

ntp

[pepedog]

I found ntpd was not reliable when I tested on the pi. openntpd worked every time, I don't see a lag with blame

[undeterminant]

It may just be my current setup; I'll try to run tests to see if it's configured wrong.

[pepedog]

There was no config needed, it might be your location?
Ditto for me with ntp?

[Kurlon]

The Pi doesn't have an RTC, so sometimes you need to bring the clock into a semblance of accuracy or NTPd will punt due to too large of an initial time shift. I call ntpdate first, then fire up ntpd.

[pepedog]

Ahh
So openntpd not prone to that?

[Kurlon]

Openntpd doesn't care about accurate timekeeping or sanity, so it doesn't have that safety built in that ntpd has. You can tell ntpd to safely take an initial large jump by starting it with -g if you want, of just use ntpdate to get the clock in the ballpark and then let ntpd dial it in.

[pepedog]

Does it warrant changing rc and .system files? What should be done for new rootfs?

[Kurlon]

I wouldn't bother, it's very much a user preference thing. For some people just running ntpdate at boot is enough, they don't even need a time daemon after that, others (like me) are time snobs and want maximum accuracy. Did I mention I have a GPS receiver for my GFN?