[time-nuts] Re: Poor's man NTP

[Hal Murray]

giuseppe at marullo.it said:
> just wondering if a PI4 could be a suitable NTP server for a small lab (and
> maybe with some other NTP servers for my company, about 2000 clients).

> Main use is for correct timestamp on logs/computer time sync. 

It should work fine.

This is the time nuts list.  You have to decide how much time you want to 
spend tuning, tweaking, and understanding NTP quirks.  It's a bottomless pit.

-------

> 0.europe.ntp.or .POOL.        ...

I think you have a typo in there.  0.europe.ntp.org doesn't exist.  Try 0.europe.pool.ntp.org

But it looks like you are getting enough servers via it.pool so you probably don't even need those lines.

------

tvb is trying to avoid this list turning into an NTP support list. 

> version="ntpd 4.2.8p12 at 1.3728-o (1)",

That's the classic Mills code.  Their support lists are broken.

I suggest switching to NTPsec.  Debian has a ntpsec package.  Their lists are working.  (Of course, as I type this, the server is down.  :)
  https://lists.ntpsec.org/

Disclaimer: I work on the NTPsec software.

-------

> BTW I don't know why reftime and clock time differs so much, and I don't know
> why the difference vary, from some seconds to several seconds if check even
> within a short time span. 

I'd have to check the code.  I think reftime is the time it last tweaked the system clock.


I can't read Italian.

I usually set things up with separate slots for the NMEA device and the PPS device, just so I can get more information.


-- 
These are my opinions.  I hate spam.