On 09/03/16 22:20, Thomas Leavitt wrote: > Hmm... looks like chronyd was installed by default under SL7 (learn > something new every day) rather than ntpd; systems seemed to still be synced > and accurate to the second. I swapped that out for ntpd. We'll see if that > makes any difference, though I doubt it. The times seemed accurate to the > second when I last looked at them. Looking at the web page for chrony, it > sounds like it is at least a functional equivalent of ntp under Linux, if not > superior in some respects. > > http://chrony.tuxfamily.org/faq.html > > No transparent proxies either, as per the network admins. Some web > filtering done via Checkpoint firewalls, but that's it. All of my SL7 boxes are using ntpd and not chronyd too. -- kind regards, David Sommerseth > -----Original Message----- > From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of Pat Riehecky > Sent: Wednesday, March 09, 2016 6:42 AM > To: Antonio Querubin; [log in to unmask] > Subject: Re: [SCIENTIFIC-LINUX-USERS] "Not using downloaded repomd.xml because it is older than what we have:" > > On 03/09/2016 03:36 AM, Antonio Querubin wrote: >> On Wed, 9 Mar 2016, John Pilkington wrote: >> >>> But doesn't SL7 use chrony? >> >> We're talking servers (ie. always on systems) right? - where >> supposedly ntpd is the better choice. I would think the mirrors are >> running ntpd instead of chronyd. >> >> But this discussion got me to rechecking again why ntpd wasn't >> starting up on some of my own servers and it turns out chronyd was >> still enabled on those. Perhaps the repo servers have the same issue? >> > I've verified that the distribution servers have a stable ntpd running and remain synced with several on site stratum1 time sources. > > Pat > ________________________________ > > This e-mail may contain privileged or confidential information. If you are not the intended recipient: (1) you may not disclose, use, distribute, copy or rely upon this message or attachment(s); and (2) please notify the sender by reply e-mail, and then delete this message and its attachment(s). EAG, Inc. and its affiliates disclaim all liability for any errors, omissions, corruption or virus in this message or any attachments. >