Hello there: Thanks so much for your time.
1. This is Linux on a x86. If you want more details, I can get that as well. 2. Sorry. I meant 1000 seconds. 3. I have verified that there are no background processes affecting system clock. I did not see any traces of someone manually changing clock by date etc., 4. Is there a way to track or log all the calls to clock_settime or any better ways to track all abrupt system clock changes? Thanks SR On Mon, Jan 27, 2020 at 6:58 PM Charles Elliott <elliott...@comcast.net> wrote: > Hello: > It is very difficult to help you if > you don't specify the platform being used, > i.e., O/S (publisher, version and updates) > and CPU if at all unusual. > > What does this mean: "more than 1000s > clock change done erroneously at the > head-end"? Does 1000s mean 1000 seconds or > is it an abbreviation for the word > "thousands"? It is common and natural (i.e., > planned that way) for NTPD to step the time > on initial startup. > > If the O/S is Windows, what does the > Event Log say? Normally, there will be a > message in the Event Log for every NTPD time > step change. > > Is there another clock program in the > system (such as Windows Time) that is also > trying to control the time, so that NTPD and > the other program are fighting? > > Have you tried a packet sniffer (such > as Wireshark) to see if an external program > is somehow affecting the time? > > Charles Elliott > > -----Original Message----- > From: questions > [mailto:questions-bounces+elliott.ch=comcast. > n...@lists.ntp.org] On Behalf Of Srihari > Raghavan > Sent: Tuesday, January 21, 2020 1:03 AM > To: questions@lists.ntp.org > Subject: [ntp:questions] Regarding > step_systime call > > Hi all > > In one of our research network lab devices, > that use an implementation based off of > ntp.org 4.2.8p12 in NTP client mode - I see a > spurious "stepped" system clock change under > certain conditions (more than 1000s clock > change done erroneously at the head-end) > BEFORE the actual NTP triggered clock change > via known NTP log message around > "step_systime" call > - and am trying to track down the spurious > clock change that happened first. There > could be other actors that could have changed > the system clock via 'date' etc., but I am > trying to rule out the obvious. > > I have added logs around step_systime call in > the code ntp_loopfilter.c and also in > ntp_timer.c and also via ntpd_time_stepped > and I don't see any of them being being > triggered for the 'spurious' case. > > Are there any other calls/paths/APIs in > NTP.org code, besides step_systime > way, that can potentially step the system > clock? Scoured the NTP.org code > (ntpdate is not being used) for the same > without success and hence my request and > email. > > Thanks in advance for any help. > > Regards > SR > _____________________________________________ > __ > questions mailing list > questions@lists.ntp.org > http://lists.ntp.org/listinfo/questions > > _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
