While monitoring NTP with Wireshark, I could see requests going out to the Internet, as well as to my local server. However, only my local server has been configured for use. Why is it going out to the net? Are there built in server names? Here are a couple of examples: jknott@linux:~> host 209.115.181.106 106.181.115.209.in-addr.arpa domain name pointer mirrors.switch.ca. jknott@linux:~> host 2606:4700:f1::123 3.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.0.0.0.0.7.4.6.0.6.2.ip6.arpa domain name pointer time.cloudflare.com. I have never configured those servers on anything I've worked on. I'm running Leap 15.3.
On 01-08-2021 18:59, James Knott wrote:
While monitoring NTP with Wireshark, I could see requests going out to the Internet, as well as to my local server. However, only my local server has been configured for use. Why is it going out to the net? Are there built in server names?
Here are a couple of examples:
jknott@linux:~> host 209.115.181.106 106.181.115.209.in-addr.arpa domain name pointer mirrors.switch.ca. jknott@linux:~> host 2606:4700:f1::123 3.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.0.0.0.0.7.4.6.0.6.2.ip6.arpa domain name pointer time.cloudflare.com.
I have never configured those servers on anything I've worked on.
I'm running Leap 15.3.
Have you checked the file /etc/chrony.d/pool.conf
On 2021-08-01 1:38 p.m., Erwin Lam wrote:
On 01-08-2021 18:59, James Knott wrote:
While monitoring NTP with Wireshark, I could see requests going out to the Internet, as well as to my local server. However, only my local server has been configured for use. Why is it going out to the net? Are there built in server names?
Here are a couple of examples:
jknott@linux:~> host 209.115.181.106 106.181.115.209.in-addr.arpa domain name pointer mirrors.switch.ca. jknott@linux:~> host 2606:4700:f1::123 3.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.0.0.0.0.7.4.6.0.6.2.ip6.arpa domain name pointer time.cloudflare.com.
I have never configured those servers on anything I've worked on.
I'm running Leap 15.3.
Have you checked the file /etc/chrony.d/pool.conf
more /etc/chrony.d/pool.conf pool 2.opensuse.pool.ntp.org iburst
I have never configured that. Any problem if I delete it?
On 01/08/2021 19.47, James Knott wrote:
On 2021-08-01 1:38 p.m., Erwin Lam wrote:
On 01-08-2021 18:59, James Knott wrote:
While monitoring NTP with Wireshark, I could see requests going out to the Internet, as well as to my local server. However, only my local server has been configured for use. Why is it going out to the net? Are there built in server names?
Here are a couple of examples:
jknott@linux:~> host 209.115.181.106 106.181.115.209.in-addr.arpa domain name pointer mirrors.switch.ca. jknott@linux:~> host 2606:4700:f1::123 3.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.0.0.0.0.7.4.6.0.6.2.ip6.arpa domain name pointer time.cloudflare.com.
I have never configured those servers on anything I've worked on.
I'm running Leap 15.3.
Have you checked the file /etc/chrony.d/pool.conf
more /etc/chrony.d/pool.conf pool 2.opensuse.pool.ntp.org iburst
I have never configured that. Any problem if I delete it?
Wait. You may have installed both ntp and chrony. Remove the package you don't use, not its files. -- Saludos/Cheers Carlos E. R.
On 2021-08-01 1:53 p.m., Carlos E.R. wrote:
I have never configured that. Any problem if I delete it? Wait.
You may have installed both ntp and chrony. Remove the package you don't use, not its files.
Chrony is installed on 2 systems and I don't ever recall installing it. Both are 15.3. I have always used ntp.
On 01/08/2021 20.13, James Knott wrote:
On 2021-08-01 1:53 p.m., Carlos E.R. wrote:
I have never configured that. Any problem if I delete it? Wait.
You may have installed both ntp and chrony. Remove the package you don't use, not its files.
Chrony is installed on 2 systems and I don't ever recall installing it. Both are 15.3. I have always used ntp.
Just as I thought, as it is the default. If you want to use ntpd, remove chrony. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-01 11:47 a.m., James Knott wrote:
On 2021-08-01 1:38 p.m., Erwin Lam wrote:
Have you checked the file /etc/chrony.d/pool.conf
more /etc/chrony.d/pool.conf pool 2.opensuse.pool.ntp.org iburst
I have never configured that. Any problem if I delete it?
Yes. That is the file that defines chrony's NTP servers. It is the default configuration. If you are using chrony, you absolutely need it, or you won't have any servers to connect to. If you are using ntp rather than chrony, remove all the chrony packages: # rpm -qa chrony* chrony-3.2-9.24.2.x86_64 chrony-pool-openSUSE-3.2-9.24.2.noarch
On 2021-08-01 2:07 p.m., Darryl Gregorash wrote:
the file that defines chrony's NTP servers. It is the default configuration. If you are using chrony, you absolutely need it, or you won't have any servers to connect to.
If you are using ntp rather than chrony, remove all the chrony packages:
I have always used ntp and didn't install chrony. How did it get there?
On 01/08/2021 20.15, James Knott wrote:
On 2021-08-01 2:07 p.m., Darryl Gregorash wrote:
the file that defines chrony's NTP servers. It is the default configuration. If you are using chrony, you absolutely need it, or you won't have any servers to connect to.
If you are using ntp rather than chrony, remove all the chrony packages:
I have always used ntp and didn't install chrony. How did it get there?
Defaults :-) -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-01 2:20 p.m., Carlos E. R. wrote:
I have always used ntp and didn't install chrony. How did it get there? Defaults:-)
So, who's the genius that decided that? Having both might cause conflicts. For example, my home server connects to 3 stratum 1 servers, owned by the Toronto Internet Exchange and 2 stratum 2 that are owned by Canada's National Research Council. Who knows where the others come from? I'll delete Chrony. BTW, many years ago, when I was running OS/2, I had my computer set up to automatically dial up a time server, though it wasn't ntp back then.
On 01/08/2021 20.36, James Knott wrote:
On 2021-08-01 2:20 p.m., Carlos E. R. wrote:
I have always used ntp and didn't install chrony. How did it get there? Defaults:-)
So, who's the genius that decided that? Having both might cause conflicts. For example, my home server connects to 3 stratum 1 servers, owned by the Toronto Internet Exchange and 2 stratum 2 that are owned by Canada's National Research Council. Who knows where the others come from?
You decided to have both >:-D openSUSE simply changed defaults. Years ago it was ntpd, currently it is chrony. New systems only have chrony, but you chose to install ntpd without removing chrony :-P
I'll delete Chrony.
BTW, many years ago, when I was running OS/2, I had my computer set up to automatically dial up a time server, though it wasn't ntp back then.
Dialup :-D And before that, on my first PC I had to type the time on every boot. People often neglected this. But mine had a CMOS clock (even being a PC, not an AT) powered by four AA batteries. An Amstrad PC 1512. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-01 2:43 p.m., Carlos E. R. wrote:
And before that, on my first PC I had to type the time on every boot. People often neglected this. But mine had a CMOS clock (even being a PC, not an AT) powered by four AA batteries. An Amstrad PC 1512.
My XT clone had the clock on one of the boards (multi I/O?) and had a BASIC program to set it.
On 01-08-2021 21:14, James Knott wrote:
On 2021-08-01 2:36 p.m., James Knott wrote:
I'll delete Chrony.
That kills ntp. So, chrony has to be installed, with it using pool.conf to select the server and a separate config for ntp to configure a server. Real genius.
Hmm, I don't know what your are doing exactly but removing chrony should not kill ntp.
On 2021-08-01 4:11 p.m., Erwin Lam wrote:
On 01-08-2021 21:14, James Knott wrote:
On 2021-08-01 2:36 p.m., James Knott wrote:
I'll delete Chrony.
That kills ntp. So, chrony has to be installed, with it using pool.conf to select the server and a separate config for ntp to configure a server. Real genius.
Hmm, I don't know what your are doing exactly but removing chrony should not kill ntp.
After removing Chrony, I went to check the NTP settings. That's when I got the warning about Chrony. I've switched 2 systems to Chrony and one's working properly, but the other, a notebook, is still getting extra servers from somewhere. Both chrony.conf and pool.conf appear to be correct and the same as the other system.
On 01/08/2021 21.14, James Knott wrote:
On 2021-08-01 2:36 p.m., James Knott wrote:
I'll delete Chrony.
That kills ntp.
No, it does not. Remove the chrony package, not the files. And of course, make sure ntpd is installed. cer@minas-tirith:~> rpm -q ntp chrony ntp-4.2.8p15-lp152.3.12.1.x86_64 chrony-3.2-lp152.13.9.1.x86_64 cer@minas-tirith:~> You only need one. At least, only one of them enabled. You may have both running by mistake, and in that case, removing chronyd would kill its ntp system, which you do not want nor care about. So, just go ahead: rpm --erase chrony no qualms. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-01 4:49 p.m., Carlos E. R. wrote:
No, it does not.
Remove the chrony package, not the files. And of course, make sure ntpd is installed.
After using Yast to unininstall chrony, I went to check the ntp settings, again in Yast. That's when I got the error message about chrony missing.
Am Sun, 1 Aug 2021 17:36:10 -0400 schrieb James Knott <james.knott@jknott.net>:
After using Yast to unininstall chrony, I went to check the ntp settings, again in Yast. That's when I got the error message about chrony missing.
YaST can most likely configure a NTP client. To do that, it tweaks files read by binaries from chrony.rpm, not from ntp.rpm. It is nowhere suggested that it would configure 'ntpd'. Also consider installing chrony-pool-empty.rpm to be able to specify your own 'server ...' configuration elements. Olaf
"OH" == Olaf Hering <olaf@aepfle.de> writes:
OH> Am Sun, 1 Aug 2021 17:36:10 -0400 schrieb James Knott OH> <james.knott@jknott.net>:
After using Yast to unininstall chrony, I went to check the ntp settings, again in Yast. That's when I got the error message about chrony missing.
OH> YaST can most likely configure a NTP client. To do that, it tweaks files OH> read by binaries from chrony.rpm, not from ntp.rpm. It is nowhere OH> suggested that it would configure 'ntpd'. OH> Also consider installing chrony-pool-empty.rpm to be able to specify your OH> own 'server ...' configuration elements. AFAIK one can configure the preferred ntp servers in the /etc/chrony.d/ directory I have done so and I can control which servers are used and which clients can query the chrony server from the local lan if they need keys or not. Just have a look to the chrony.conf man page and write your own configuration HTH
On 02/08/2021 00.42, Togan Muftuoglu wrote:
"OH" == Olaf Hering <olaf@aepfle.de> writes:
OH> Am Sun, 1 Aug 2021 17:36:10 -0400 schrieb James Knott OH> <james.knott@jknott.net>:
After using Yast to unininstall chrony, I went to check the ntp settings, again in Yast. That's when I got the error message about chrony missing.
OH> YaST can most likely configure a NTP client. To do that, it tweaks files OH> read by binaries from chrony.rpm, not from ntp.rpm. It is nowhere OH> suggested that it would configure 'ntpd'.
OH> Also consider installing chrony-pool-empty.rpm to be able to specify your OH> own 'server ...' configuration elements.
AFAIK one can configure the preferred ntp servers in the /etc/chrony.d/ directory I have done so and I can control which servers are used and which clients can query the chrony server from the local lan if they need keys or not.
Just have a look to the chrony.conf man page and write your own configuration
The assumption is that James wants to configure ntpd, not chrony. If that is not the case, James, speak up. Choose: either the old and classic ntpd daemon, or the new chronyd daemon. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-01 8:52 p.m., Carlos E. R. wrote:
Just have a look to the chrony.conf man page and write your own configuration The assumption is that James wants to configure ntpd, not chrony.
If that is not the case, James, speak up. Choose: either the old and classic ntpd daemon, or the new chronyd daemon.
I had been using NTP, but have switched to Chrony.
On 02/08/2021 15.02, James Knott wrote:
On 2021-08-01 6:42 p.m., Togan Muftuoglu wrote:
AFAIK one can configure the preferred ntp servers in the/etc/chrony.d/ directory I have done so
I have done that. One system now works as expected, but one (ThinkPad) is still getting extraneous addresses from somewhere.
Make sure it doesn't have both chrony and ntpd. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-01 6:00 p.m., Olaf Hering wrote:
Am Sun, 1 Aug 2021 17:36:10 -0400 schrieb James Knott <james.knott@jknott.net>:
After using Yast to unininstall chrony, I went to check the ntp settings, again in Yast. That's when I got the error message about chrony missing. YaST can most likely configure a NTP client. To do that, it tweaks files read by binaries from chrony.rpm, not from ntp.rpm. It is nowhere suggested that it would configure 'ntpd'.
NTP configuration is in Yast > Network Services. However, after uninstalling NTP and it's Yast module, it's still there, but doesn't anything. Maybe it will disappear after rebooting.
Also consider installing chrony-pool-empty.rpm to be able to specify your own 'server ...' configuration elements.
I just edited the one that pointed to opensuse.pool.ntp.org.
On 2021-08-02 9:00 a.m., James Knott wrote:
NTP configuration is in Yast > Network Services. However, after uninstalling NTP and it's Yast module, it's still there, but doesn't anything. Maybe it will disappear after rebooting.
Yep, it does and also doesn't work after reinstalling without a reboot. I used it to add another server, which shows up in Wireshark, but I don't see where it's saved. It's not in ntp.conf (doesn't exist), crony.conf or pool.conf
On 02/08/2021 16.29, James Knott wrote:
On 2021-08-02 9:00 a.m., James Knott wrote:
NTP configuration is in Yast > Network Services. However, after uninstalling NTP and it's Yast module, it's still there, but doesn't anything. Maybe it will disappear after rebooting.
Yep, it does and also doesn't work after reinstalling without a reboot. I used it to add another server, which shows up in Wireshark, but I don't see where it's saved. It's not in ntp.conf (doesn't exist), crony.conf or pool.conf
Find out the process and its parameters: ps afxu | grep chrony Maybe nothing, maybe a clue. Maybe there is some other configuration place. -- Saludos/Cheers Carlos E. R.
On 02/08/2021 16.38, James Knott wrote:
On 2021-08-02 10:31 a.m., Carlos E.R. wrote:
ps afxu | grep chrony
At first glance, I thought that meant ps all f*cked up. ;-)
Anyway, all it shows is chronyd.
Without parameters? have a look then at /usr/lib/systemd/system/chronyd.service, another obvious file ;-) It mentions another configuration file (just a bit less obtious). -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-02 10:45 a.m., Carlos E. R. wrote:
On 02/08/2021 16.38, James Knott wrote:
On 2021-08-02 10:31 a.m., Carlos E.R. wrote:
ps afxu | grep chrony At first glance, I thought that meant ps all f*cked up.;-)
ps afxu |grep chrony chrony 1391 0.0 0.0 90484 2356 ? S 09:48 0:00 /usr/sbin/chronyd jknott 5174 0.0 0.0 10128 652 pts/5 S+ 10:47 0:00 \_ grep --color=auto chrony
On 02/08/2021 16.52, James Knott wrote:
On 2021-08-02 10:45 a.m., Carlos E. R. wrote:
have a look then at /usr/lib/systemd/system/chronyd.service, another obvious file;-)
It mentions another configuration file (just a bit less obtious).
Yep, so less obvious I can't see anything.
Common! :-) The service is oviously named "chronyd.service". You can learn the location in the list of files in the rpm: minas-tirith:~ # rpm -ql chrony | grep service /usr/lib/systemd/system/chrony-dnssrv@.service /usr/lib/systemd/system/chrony-wait.service /usr/lib/systemd/system/chronyd.service <===== /usr/share/doc/packages/chrony/examples/chrony-wait.service /usr/share/doc/packages/chrony/examples/chronyd.service minas-tirith:~ # Or: minas-tirith:~ # locate chronyd.service /usr/lib/systemd/system/chronyd.service /usr/share/doc/packages/chrony/examples/chronyd.service minas-tirith:~ # Or, without knowing the actual location: minas-tirith:~ # systemctl cat chronyd # /usr/lib/systemd/system/chronyd.service [Unit] Description=NTP client/server Documentation=man:chronyd(8) man:chrony.conf(5) After=nss-lookup.target Wants=network.target After=network.target Wants=time-sync.target Before=time-sync.target Conflicts=ntpd.service systemd-timesyncd.service ConditionCapability=CAP_SYS_TIME [Service] Type=forking PIDFile=/run/chronyd.pid EnvironmentFile=-/etc/sysconfig/chronyd <============ ExecStart=/usr/sbin/chronyd $OPTIONS <============ ExecStartPost=/usr/lib/chrony/helper update-daemon PrivateTmp=yes ProtectHome=yes ProtectSystem=full minas-tirith:~ # See? You can see how the daemon command is actually executed, and where do the $OPTIONS come from. In my case, there is nothing: minas-tirith:~ # grep OPTIONS /etc/sysconfig/chronyd minas-tirith:~ # But anyway, have a look at the file, there are other entries that might interest you. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Apparently James and Carlos are not using systemd-timesyncd.service as I am trying to, since I'm also using systemd-networkd instead of NM or Wicked: # systemctl list-unit-files | egrep 'hron|ntp|times|wick|rkMana' chrony-dnssrv@.service static - chrony-wait.service disabled disabled chronyd.service enabled disabled systemd-timesyncd.service enabled disabled chrony-dnssrv@.timer disabled disabled # rpm -ql systemd | grep timesy /etc/systemd/timesyncd.conf /usr/lib/systemd/ntp-units.d/80-systemd-timesync.list /usr/lib/systemd/system/systemd-timesyncd.service /usr/lib/systemd/systemd-timesyncd /usr/share/dbus-1/system-services/org.freedesktop.timesync1.service /usr/share/dbus-1/system.d/org.freedesktop.timesync1.conf /usr/share/man/man5/timesyncd.conf.5.gz /usr/share/man/man5/timesyncd.conf.d.5.gz /usr/share/man/man8/systemd-timesyncd.8.gz /usr/share/man/man8/systemd-timesyncd.service.8.gz # cat /usr/lib/systemd/ntp-units.d/80-systemd-timesync.list # This file is part of systemd. # See systemd-timedated.service(8) for more information. systemd-timesyncd.service # cat /etc/systemd/timesyncd.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it under the # terms of the GNU Lesser General Public License as published by the Free # Software Foundation; either version 2.1 of the License, or (at your option) # any later version. # # Entries in this file show the compile time defaults. Local configuration # should be created by either modifying this file, or by creating "drop-ins" in # the timesyncd.conf.d/ subdirectory. The latter is generally recommended. # Defaults can be restored by simply deleting this file and all drop-ins. # # See timesyncd.conf(5) for details. [Time] #NTP= #FallbackNTP=time1.google.com time2.google.com time3.google.com time4.google.com #RootDistanceMaxSec=5 #PollIntervalMinSec=32 #PollIntervalMaxSec=2048 I too am trying to override the defaults, switching to *.pool.ntp.org, with no luck so far trying to learn where the defaults are ensconced. So far I have learned that changing the #NTP= line to NTP=0.us.pool.ntp.org 1.us.pool.ntp.org 2.us.pool.ntp.org 3.us.pool.ntp.org apparently doesn't work. Restoring the file and creating /etc/systemd/timesyncd.conf.d/10-override.conf containing only NTP=0.us.pool.ntp.org 1.us.pool.ntp.org 2.us.pool.ntp.org 3.us.pool.ntp.org apparently doesn't work either: # systemctl status systemd-timesyncd ○ systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-timesyncd.service(8) -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 02/08/2021 22.38, Felix Miata wrote:
Apparently James and Carlos are not using systemd-timesyncd.service as I am trying to, since I'm also using systemd-networkd instead of NM or Wicked:
# systemctl list-unit-files | egrep 'hron|ntp|times|wick|rkMana' chrony-dnssrv@.service static - chrony-wait.service disabled disabled chronyd.service enabled disabled systemd-timesyncd.service enabled disabled chrony-dnssrv@.timer disabled disabled
What are the second and third columns? I only get two columns on that command ('unit file' and 'status'). -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. composed on 2021-08-03 01:10 (UTC+0200):
Felix Miata wrote:
Apparently James and Carlos are not using systemd-timesyncd.service as I am trying to, since I'm also using systemd-networkd instead of NM or Wicked:
# systemctl list-unit-files | egrep 'hron|ntp|times|wick|rkMana' chrony-dnssrv@.service static - chrony-wait.service disabled disabled chronyd.service enabled disabled systemd-timesyncd.service enabled disabled chrony-dnssrv@.timer disabled disabled
What are the second and third columns? I only get two columns on that command ('unit file' and 'status').
# grep e:t /etc/os-release CPE_NAME="cpe:/o:opensuse:tumbleweed:20210730" # systemctl list-unit-files | head -n2 UNIT FILE STATE VENDOR PRESET proc-sys-fs-binfmt_misc.automount static - -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 03/08/2021 01.25, Felix Miata wrote:
Carlos E. R. composed on 2021-08-03 01:10 (UTC+0200):
Felix Miata wrote:
Apparently James and Carlos are not using systemd-timesyncd.service as I am trying to, since I'm also using systemd-networkd instead of NM or Wicked:
# systemctl list-unit-files | egrep 'hron|ntp|times|wick|rkMana' chrony-dnssrv@.service static - chrony-wait.service disabled disabled chronyd.service enabled disabled systemd-timesyncd.service enabled disabled chrony-dnssrv@.timer disabled disabled
What are the second and third columns? I only get two columns on that command ('unit file' and 'status').
# grep e:t /etc/os-release CPE_NAME="cpe:/o:opensuse:tumbleweed:20210730" # systemctl list-unit-files | head -n2 UNIT FILE STATE VENDOR PRESET proc-sys-fs-binfmt_misc.automount static -
ok, so you have both enabled chronyd.service and systemd-timesyncd.service. But, you shouldn't: minas-tirith:~ # systemctl cat chronyd.service | grep -i conflict Conflicts=ntpd.service systemd-timesyncd.service minas-tirith:~ # There is your problem. -- Saludos/Cheers Carlos E. R.
On 01/08/2021 23.36, James Knott wrote:
On 2021-08-01 4:49 p.m., Carlos E. R. wrote:
No, it does not.
Remove the chrony package, not the files. And of course, make sure ntpd is installed.
After using Yast to unininstall chrony, I went to check the ntp settings, again in Yast. That's when I got the error message about chrony missing.
So? Forget yast and configure ntp by hand, it is not that difficult. I have not looked, but it is possible that yast is designed today to handle only chrony, while in the past it would only handle ntpd. You could have a look in YaST to see if you can tell YaST to configure ntpd instead. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-01 8:47 p.m., Carlos E. R. wrote:
So? Forget yast and configure ntp by hand, it is not that difficult.
I have not looked, but it is possible that yast is designed today to handle only chrony, while in the past it would only handle ntpd. You could have a look in YaST to see if you can tell YaST to configure ntpd instead.
Since chrony is now default, maybe Yast should have been properly updated. Leaving it this way creates a mess, where you're not sure what's happening. With chrony, the only way to set a server appears to be editing either chrony.conf or pool .conf. There doesn't seem to be anything in Yast, where one might expct settings to be. Sure, it's easy enough to edit files, but that requires knowing about those files. There are many situations where a local server is supposed to be used, such as in business networks, so hiding the config is not a good idea. I run into similar with my Asus table. The NTP server is somewhere in Asia and there doesn't appear to be any way to change it. My solution was to create a DNS alias to send it to my server. If you're going to create a default server, make it pool.ntp.org and nothing else. It uses geolocation to use a reasonably nearby server. I have no idea where opensuse.pool.ntp.org is located, but I bet it's not in Canada. The stratum 1 servers I connect to are located in Toronto, which is the next city over (in fact, located in the building where I worked for 17 years).
On 02/08/2021 15.17, James Knott wrote:
On 2021-08-01 8:47 p.m., Carlos E. R. wrote:
So? Forget yast and configure ntp by hand, it is not that difficult.
I have not looked, but it is possible that yast is designed today to handle only chrony, while in the past it would only handle ntpd. You could have a look in YaST to see if you can tell YaST to configure ntpd instead.
Since chrony is now default, maybe Yast should have been properly updated. Leaving it this way creates a mess, where you're not sure what's happening.
I see on 15.2 that there is a yast2-ntp-client, but I don't use it. I configure ntpd by editing its configuration files. I don't see in 15.2 a similar module for chrony, maybe 15.3 has it. .
With chrony, the only way to set a server appears to be editing either chrony.conf or pool .conf. There doesn't seem to be anything in Yast, where one might expct settings to be. Sure, it's easy enough to edit files, but that requires knowing about those files.
Well, the same thing happens for any service in Linux :-)
There are many situations where a local server is supposed to be used, such as in business networks, so hiding the config is not a good idea.
It is not hidden! If I want to configure chrony, I will immediately look for some file or directory named chrony under /etc/, so I will do, the first minute: ls /etc/chrony* Then i will have a look at the file(s) I find, and, if I don't understand it, I will read the manual. The configuration file is in the obvious location. If the file would be "/etc/timesync", that would not be obvious :-)
I run into similar with my Asus table. The NTP server is somewhere in Asia and there doesn't appear to be any way to change it. My solution was to create a DNS alias to send it to my server. If you're going to create a default server, make it pool.ntp.org and nothing else. It uses geolocation to use a reasonably nearby server. I have no idea where opensuse.pool.ntp.org is located, but I bet it's not in Canada. The stratum 1 servers I connect to are located in Toronto, which is the next city over (in fact, located in the building where I worked for 17 years).
Well, opensuse.pool.ntp.org is currently broken. minas-tirith:~ # host opensuse.pool.ntp.org minas-tirith:~ # so I can not verify it. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-02 10:08 a.m., Carlos E. R. wrote:
There are many situations where a local server is supposed to be used, such as in business networks, so hiding the config is not a good idea. It is not hidden!
If I want to configure chrony, I will immediately look for some file or directory named chrony under/etc/, so I will do, the first minute:
That assumes you know about chrony. Until yesterday, I didn't know it was default.
On 02/08/2021 16.18, James Knott wrote:
On 2021-08-02 10:08 a.m., Carlos E. R. wrote:
There are many situations where a local server is supposed to be used, such as in business networks, so hiding the config is not a good idea. It is not hidden!
If I want to configure chrony, I will immediately look for some file or directory named chrony under/etc/, so I will do, the first minute:
That assumes you know about chrony. Until yesterday, I didn't know it was default.
I know nothing about chrony, only its existence, and some comments here in the lists. I know that if I find myself in the need to configure "foodaemon", I will instantly look to find /etc/foodaemon. It is the obvious location for a system (not user) daemon. I would also expect it to be started by "systemctl start foodaemon". -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-08-02 10:25 a.m., Carlos E. R. wrote:
I know that if I find myself in the need to configure "foodaemon", I will instantly look to find /etc/foodaemon. It is the obvious location for a system (not user) daemon.
I would also expect it to be started by "systemctl start foodaemon".
Again, I didn't know about chrony until yesterday. I have always used ntp, so why would I look for chrony when I didn't know about it?
On 02/08/2021 16.30, James Knott wrote:
On 2021-08-02 10:25 a.m., Carlos E. R. wrote:
I know that if I find myself in the need to configure "foodaemon", I will instantly look to find /etc/foodaemon. It is the obvious location for a system (not user) daemon.
I would also expect it to be started by "systemctl start foodaemon".
Again, I didn't know about chrony until yesterday. I have always used ntp, so why would I look for chrony when I didn't know about it?
Sure. But once we tell you that there is another service called "chrony" and that it is the default for ntp, the obvious configuration file is in /etc/chrony* If the obvious does not exist, you can do "rpm -ql chrony" to find the list of files. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 8/1/21 9:59 AM, James Knott wrote:
While monitoring NTP with Wireshark, I could see requests going out to the Internet, as well as to my local server. However, only my local server has been configured for use. Why is it going out to the net? Are there built in server names?
Here are a couple of examples:
jknott@linux:~> host 209.115.181.106 106.181.115.209.in-addr.arpa domain name pointer mirrors.switch.ca. jknott@linux:~> host 2606:4700:f1::123 3.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.0.0.0.0.7.4.6.0.6.2.ip6.arpa domain name pointer time.cloudflare.com.
I have never configured those servers on anything I've worked on.
I'm running Leap 15.3.
Many, if not most, distros have a set off publicly available pooled server pre-configured, be it with chrony or "classic" ntpd. If ntpd look at /etc/ntp.conf if chrony look at /etc/chrony.conf
On 2021-08-01 8:10 p.m., Bruce Ferrell wrote:
Many, if not most, distros have a set off publicly available pooled server pre-configured, be it with chrony or "classic" ntpd.
If ntpd look at /etc/ntp.conf
if chrony look at /etc/chrony.conf
After switching to crony, ntp.conf is gone. I have edited pool.conf. Chrony.conf has a link to opensuse.pool.ntp.org, but is prepended with ! which I assume blocks it.
participants (9)
-
Bruce Ferrell -
Carlos E. R. -
Carlos E.R. -
Darryl Gregorash -
Erwin Lam -
Felix Miata -
James Knott -
Olaf Hering -
Togan Muftuoglu