Skip to main content ↑ ↓
Topic: Proper NTP Settings -GUI vs Runit & NTP.conf vs Stubby (Read 643 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Proper NTP Settings -GUI vs Runit & NTP.conf vs Stubby

Hi,

I recently got 1 hour time difference on my systray clock vs real local time. (its not about winter time change)

So by comparison:

1. Debian/Ubuntu etc. sytemdtimesyncd you set up your NTP servers there and you're good to go.
KDE has no problem with it. You can put IPs in KDE GUI (right click in "systray" and put serevers there)

2. On Devuan, KDE's time syncing GUI is grayed out (you cannot type in your NTP servers IPs). I set up use OpenRC deamon that OpenBSD uses. No problem whatsoever. Uses this drift mode. And time syncs some time after boot. No immediate. Good. Working.

3. On KDE Artix with runit, KDE GUIs for typing in your NTP servers IPs is not grayed out. Normally (by default on Artix) we have:
$ sv status ntp does not give anything. Deamon is not working. Just like on Devuan.

My question is the following: WHAT IS KDE USING TO SYNC TIME in IT'S GUI? DOES IT RUN ANY DEAMON ON ITS OWN ??
I put in KDE's GUI my NTP IPs and that's it. But apparently it may not work as a deamon and may (doesn't) sync the time. If you untick and tick again and press OK/Apply, KDE will sync. But question is only this one time time?

Shouldn't it be grayed out in KDE's GUI (like in Devuan)?  Or KDE is using some internal mechanism to sync time from time to time?

So what is the correct procedure to set up timesyncing on Artix KDE runit?

There's more:

ntp.conf has the following line:
restrict default kod limited nomodify nopeer noquery notrap
restrict 127.0.0.1
restrict ::1

So my network manger had 127.0.0.1 and ::1 because I run stubby for my DNSes.

So now WHAT IS THE CORRECT WAY OF SETTING TIMESYNC ON ARTIX WITH RUNIT, KDE AND STUBBY?

Re: Proper NTP Settings -GUI vs Runit & NTP.conf vs Stubby

Reply #1 –
I have artix + runit. I don't use KDE though.

On my system the ntp daemon is called ntpd so this works

Code: [Select]
$ sudo sv status ntpd
run: ntpd: (pid 1433) 41s

and date appears to be OK

Code: [Select]
$ date
Wed  6 Dec 13:52:47 GMT 2023
$ date -u
Wed  6 Dec 13:52:55 UTC 2023

the tint2 clock I have in openbox appears to be working correctly in the Europe/London timezone as does xclock etc etc.


Re: Proper NTP Settings -GUI vs Runit & NTP.conf vs Stubby

Reply #2 –
Not sure if you have done this, but you need to install either the ntp or openntpd package, and then install and enable the service for your init which is a separate package, ie for runit, ntp-runit or openntpd-runit. openntpd is an alternative BSD licensed implementation of ntp provided by OpenBSD.

Re: Proper NTP Settings -GUI vs Runit & NTP.conf vs Stubby

Reply #3 –
Quote from: sonar – on
There's more:

ntp.conf has the following line:
restrict default kod limited nomodify nopeer noquery notrap
restrict 127.0.0.1
restrict ::1

So my network manger had 127.0.0.1 and ::1 because I run stubby for my DNSes.
Two different concepts
IP address https://en.wikipedia.org/wiki/IP_address
Port https://en.wikipedia.org/wiki/Port_(computer_networking)

Personally I just have
Code: [Select]
ntpdate  -b -s -u 0.uk.pool.ntp.org &
run at every boot. No running service needed unless you don't reboot for month's on end or the clock is highly inaccurate.

Re: Proper NTP Settings -GUI vs Runit & NTP.conf vs Stubby

Reply #4 –
Now I have KDE's settings grayed-out. Apparently KDE's clock/sync GUI is ONLY SYSTEMD.

So I run opnntpd, but still have some problems and CANNOT SYNC THE CLOCK.

I hashed "constraints" as apparently they are only for TLS date and not needed, tbh. (and I do not want default NSA google or quad and obviously NOT cloudflare).

My ntp servers are valitd. Both. But the clock remaines unsynced:

$ ntpctl -s all gives the follwing:

2/2 peers valid, clock unsynced

peer
   wt tl st  next  poll          offset       delay      jitter
xxx.xxx.xx
    1 10  1   27s   30s       589.732ms    21.777ms     2.925ms
xxx.xxx..xx
    1 10  1   22s   34s       590.515ms    22.862ms     4.716ms

So peers are valid, but clocks remains unsynced (chcecked multiple times, waited, etc). Why? Anyone any idea?

Re: Proper NTP Settings -GUI vs Runit & NTP.conf vs Stubby

Reply #5 –
If KDE has a systemd service to do this, if you found the service file then looked at what command it runs you might be able to replicate it in a runit service.