On Thu, Dec 3, 2020 at 12:47 AM Jerry Geis wrote:
> So ntpdate is no longer present past CentOS 7.
>
> Many times people want "internal" NTP servers - not opening firewalls to
> allow external pool.ntp.org kind of stuff.
>
> ntpdate was "nice" in that I could just run once a day as "ntpdate
On Thu, Dec 03, 2020 at 07:06:25AM +, J Martin Rushton via CentOS wrote:
> On 02/12/2020 23:32, Brian Reichert wrote:
> >On Wed, Dec 02, 2020 at 02:17:04PM -0500, Jerry Geis wrote:
> >>So ntpdate is no longer present past CentOS 7.
> >
> >What's wrong with the 'ntpdate' RPM?
> >
>
On 02/12/2020 23:32, Brian Reichert wrote:
On Wed, Dec 02, 2020 at 02:17:04PM -0500, Jerry Geis wrote:
So ntpdate is no longer present past CentOS 7.
What's wrong with the 'ntpdate' RPM?
https://centos.pkgs.org/7/centos-x86_64/ntpdate-4.2.6p5-29.el7.centos.2.x86_64.rpm.html
What's wrong is
On Wed, Dec 02, 2020 at 02:17:04PM -0500, Jerry Geis wrote:
> So ntpdate is no longer present past CentOS 7.
What's wrong with the 'ntpdate' RPM?
https://centos.pkgs.org/7/centos-x86_64/ntpdate-4.2.6p5-29.el7.centos.2.x86_64.rpm.html
> Thanks,
>
> Jerry
>
and I'm doing much the same: a Raspberry Pi running Raspbian, acts as my
nameserver (instead of my ISP) and NTP server. all the systems in-house
sync time from it.
On Wed, Dec 2, 2020 at 3:22 PM Bill Gee wrote:
> What IS in your chrony.conf file?
>
> "pool.ntp.org" is not a single server. It
What IS in your chrony.conf file?
"pool.ntp.org" is not a single server. It is a collection of several dozen.
When you specify a pool of servers for chrony, it will pick 4 mostly at random
and use those. The four servers it chooses will change over time.
If you want to use exactly one
Thanks everyone for the comments. So trying to use the new "chronyc/d"
So trying a couple things with chronyc
chronyc sources
210 Number of sources = 5
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
On Wed, Dec 2, 2020 at 1:26 PM John Pierce wrote:
> the problem with that sort of time sync is that if your systems clock is
> running fast, then those once a day time syncs cause the clock to be set
> BACK a few seconds or whatever (in bad cases a few minutes).
>
Modern chrony that Bill Gee
On Wed, Dec 2, 2020 at 11:17 AM Jerry Geis wrote:
> ...
> ntpdate was "nice" in that I could just run once a day as "ntpdate name"
the problem with that sort of time sync is that if your systems clock is
running fast, then those once a day time syncs cause the clock to be set
BACK a few
There is a command-line option for chronyd which runs once, sets the time and
exits.
# chronyd -q
I run chrony as a daemon on all my systems. One system is a server to
everything else that is internal. The server is the only one that goes
outside. It works well. The initial setup
So ntpdate is no longer present past CentOS 7.
Many times people want "internal" NTP servers - not opening firewalls to
allow external pool.ntp.org kind of stuff.
ntpdate was "nice" in that I could just run once a day as "ntpdate name"
and all good. Is there a similar client for CentOS 8 ? I saw
11 matches
Mail list logo
