[opensuse] ntp synchronizes to broadcast source despite no configuration ??
Trying to disprove Carlos' suggestion that the kernel "knows" about leap seconds, I installed a Leap421 desktop, at first leaving out ntp, then installing it later. To avoid the time being set on startup (with sntp), I created # l `which sntp` lrwxrwxrwx 1 root root 13 Jan 6 18:05 /usr/sbin/sntp -> /usr/bin/true* I was a bit surprised to see ntpd being started with '-g' anyway, which meant setting the time as well, I amend ed/etc/sysconfig/ntp to prevent that. My ntp.config: --------------- server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized driftfile /var/lib/ntp/drift/ntp.drift logfile /var/log/ntp logconfig =all --------------------- Seems to me that ought to be good for a stand-alone ntpd. However, a little while after starting it: # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 .LOCL. 10 l 546 64 0 0.000 0.000 0.000 *192.168.2.254 .DCFa. 1 u 66 64 377 0.239 -4.834 4.087 Surely that is not correct. -- Per Jessen, Zürich (-6.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 06-01-17 om 18:34 schreef Per Jessen: ...
Seems to me that ought to be good for a stand-alone ntpd. However, a little while after starting it:
# ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 .LOCL. 10 l 546 64 0 0.000 0.000 0.000 *192.168.2.254 .DCFa. 1 u 66 64 377 0.239 -4.834 4.087
Surely that is not correct.
Per, DHCP sending an ntp-server ? Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong wrote:
Op 06-01-17 om 18:34 schreef Per Jessen: ...
Seems to me that ought to be good for a stand-alone ntpd. However, a little while after starting it:
# ntpq -pn remote refid st t when poll reach delay offset jitter
==============================================================================
127.127.1.0 .LOCL. 10 l 546 64 0 0.000 0.000 0.000 *192.168.2.254 .DCFa. 1 u 66 64 377 0.239 -4.834 4.087
Surely that is not correct.
Per,
DHCP sending an ntp-server ?
Koenraad
Hi Koenraad yes, well spotted, but I think I took care of it :-) For this machine, I added "option time-servers none" to the dhcp config. I'm not sure if that worked though, will have to double check. Err, yes, you were right - Jan 1 00:50:55 office31 logger[1461]: runtime configuration: server 192.168.2.254 So my dhcp config isn't working the way I expect it too. -- Per Jessen, Zürich (-7.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-06 18:34, Per Jessen wrote:
Trying to disprove Carlos' suggestion that the kernel "knows" about leap seconds, I installed a Leap421 desktop, at first leaving out ntp, then installing it later.
:-) I tried also on a laptop running a test of 42.2. I simply stopped ntp daemon, then set the time back. Crash! went the desktop. I'm unsure of the result. I want to repeat with a longer run, not just two hours. I want to try a virtual machine, but I have to stop both ntp and the vmware client tools. You could block ntp packages on the firewall. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-01-06 18:34, Per Jessen wrote:
Trying to disprove Carlos' suggestion that the kernel "knows" about leap seconds, I installed a Leap421 desktop, at first leaving out ntp, then installing it later.
:-)
I tried also on a laptop running a test of 42.2. I simply stopped ntp daemon, then set the time back. Crash! went the desktop.
I'm unsure of the result. I want to repeat with a longer run, not just two hours. I want to try a virtual machine, but I have to stop both ntp and the vmware client tools.
To set the time, at first I set it in the BIOS on startup, but after having ntp set it back to normal a few times, I switched to: date -u 123100502016 hwclock --systohc For now, it looks like it's working - not sure why. The time-server is being handed out by dhcp, but now it's not being added to the ntp config locally. # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 2 64 3 0.000 0.000 0.000 # date Sun 1 Jan 00:52:48 CET 2017 So in about 7 minutes, there should be a leap second. -- Per Jessen, Zürich (-7.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-07 09:55, Per Jessen wrote:
Carlos E. R. wrote:
To set the time, at first I set it in the BIOS on startup, but after having ntp set it back to normal a few times, I switched to:
date -u 123100502016 hwclock --systohc
For now, it looks like it's working - not sure why. The time-server is being handed out by dhcp, but now it's not being added to the ntp config locally.
ntp aborts if the time difference is too big. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-01-07 09:55, Per Jessen wrote:
Carlos E. R. wrote:
To set the time, at first I set it in the BIOS on startup, but after having ntp set it back to normal a few times, I switched to:
date -u 123100502016 hwclock --systohc
For now, it looks like it's working - not sure why. The time-server is being handed out by dhcp, but now it's not being added to the ntp config locally.
ntp aborts if the time difference is too big.
Yes, but that is not what's happening. ntp is running just fine. Anyway, it's not important anymore. -- Per Jessen, Zürich (-4.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Carlos E. R. -
Koenraad Lelong -
Per Jessen