Description:
The network time protocol.
|
|
|
ntpd connect gpsd shared memory driver
|
| |
Based on poor luck with ntpd/pps, I'm trying to have ntpd use the shared
memory driver provided by gpsd. Do I need to give a special flag to
configure for ntp to tell it to build in support for the shared memory
driver?
Using this for my ntp.conf
---
server 127.127.28.0 minpoll 4
fudge 127.127.28.0 refid NMEA... more »
|
|
|
pps breaks when nmea is enabled for ntpd
|
| |
I have a TI DM8168 processor and a u-blox gps.
If I enable an internet server and pps, then pps works great
server clock.redhat.com iburst prefer minpoll 4 maxpoll 4
server 127.127.22.0 minpoll 4 maxpoll 4
fudge 127.127.22.0 flag3 1
However, if I add an NMEA server to my ntp.conf file like this... more »
|
|
|
ntp-b.boulder.nist.gov not synchronized
|
| |
Since about 1800 Eastern time (US) on 10Jun, ntp-a.boulder.nist.gov is sending "clock unsynchronized". This is one of two NIST-supported, _authenticated_, timeservers (the other is ntp-b.nist.gov).
We are regulatorily required to confirm twice daily that our system's time (derived from GPS) is within 1 second of "official" US Gov't time... more »
|
|
|
Standalone PPS
|
| |
Hello
I would like to get some points of view before starting to write some code.
I am trying run an electronic board I designed.
A super stable OXCO generates pulse per second.
I don't have any absolute reference time. The pulse has a constant but unpredictable phase due to the state of the electronics a power up.... more »
|
|
|
NTP Server Synchronizing with the incorrect NTP server
|
| |
Problem:
I configured my NTP server in Linux to use the US Pool of NTP Servers in /etc/ntp.conf. I restarted the NTP service many times and the actual server many times, but it was not using the pool. I was verifying this by using the ntpq -p command. It was using a time server it picked up via DHCP when it was plugged into a completely different network. I had no idea where it was getting this information.... more »
|
|
|
Behaved ... Limited ... KODed
|
| |
Hello,
I thought I understood how a client's rate control indicator goes from being
well behaved (.) to limited (L) to KoD (K) but after trying to explain this to
someone today it is obvious that I do not. A server running the most recent dev
release (or post whatever version changed minimum to seconds instead of 2**n)... more »
|
|
|
Sudden change in precision and jitter
|
| |
I restarted ntpd early this morning (no configuration changes, just rolling a log and it's been running for over 12 hours now), but for some reason, for the first time, it recomputed the precision to -12 (used to be -13) and the jitter on PPS is now reaching a floor value of 0.000244141 which is exactly double (with a slight rounding error) of... more »
|
|
|
