Re: NTP sets clock backwards

From: Andreas Schulze (b79xan_at_gmx.de)
Date: 11/28/03

  • Next message: Paul Pluzhnikov: "Re: Undefined symbol problems with the run time linker"
    Date: Fri, 28 Nov 2003 17:09:02 +0100
    
    

    "Nick" <nick.skingle@ftid.com> schrieb im Newsbeitrag
    news:ed7b1c4.0311280730.6a1b1381@posting.google.com...
    > Is there any way to stop xntpd from setting the time backwards. I have
    > heard there is an undocumented -x flag, but our ntp clients are within
    > an SP environment and xntpd is started from the resource controller.
    > Any comments and suggestions with regards to the way ntp keeps time
    > would be appreciated
    >
    > Thanks
    > Nick

    Hallo Nick,

    you did not write which oslevel you use. Thus some thoughts based on
    assumptions only: AIX xntpd sets time backwards if time difference to time
    server becomes >= 1 second. Problem is, that time is switched back in 'step'
    (of full seconds). This leads to problems as then a program might end before
    it started, e.g. if timestep back ocurred while program was running. You can
    watch this in the system log. Great fun when using SAP or running certain
    programs - NOT. The undocumented x-flag is not there. At least it was not
    there with xntpd 3.4y (I stopped using AIX xntpd since).
    So what to do? Solution is easy: get ntpd from http://www.ntp.org/
    This ntpd (Ver. 4 or later) can 'slew' the time (by using the '-x' option
    you mentioned) and replaces the AIX xntpd perfectly. I had to compile it and
    did so with gcc. Worked perfectly for me.

    # stopsrc -s xntpd
    # The Subsystem xntpd was successfully requested to stop
    # /usr/local/ntp4/bin/ntpd -x

    Best thing is to start ntpd from /etc/inittab (with a sleep 1 between the
    stop of xntpd and start of ntpd). Make sure , that only one ntpd is running.
    Should you happen to have started ntpd after xntpd (e.g. both are up and
    running) it is not enough to stop xntpd but you need to stop and start ntpd
    again, too.

    Search this group for further details.

    HTH,
    Andreas


  • Next message: Paul Pluzhnikov: "Re: Undefined symbol problems with the run time linker"

    Relevant Pages

    • Re: Time steping regardless of "-x" slew only option
      ... In ntpd the -x otion is still there, but has a slightly different interpretation. ... The xntpd and early ntpd used a different feedback loop for ordinary and slew modes. ... In this design a step forward is implemented directly, but a step backward up to one second causes the system clock to stop for one second or increment slowly during that second. ... I only have one time server, ...
      (comp.protocols.time.ntp)
    • Re: Correcting my time servers clock drift on Alpha ES40s / Tru64
      ... Whether xntpd or NTPv4 is supported in Linux has nothing to do with me or the Corps, but the only version we support is ntpd. ... The online documentation relates to the current snapshot; the distribution documentation relates to that specific distribution. ...
      (comp.protocols.time.ntp)
    • Re: Ntpd assistance
      ... > Correct me if I'm wrong but doesn't ntpd 4.1 use ntp.conf instead of ... In addition to this minor error ... ... I don't believe you can reliably run both ntpdate and xntpd. ...
      (freebsd-questions)
    • Re: ntp_gettime - reconnect
      ... xntpd is either seriously obsolete or misnamed. ... No version of ntpd uses connection oriented protocols, ...
      (comp.protocols.time.ntp)
    • Re: ntp_gettime - reconnect
      ... xntpd is either seriously obsolete or misnamed. ... No version of ntpd uses connection oriented protocols, ...
      (comp.protocols.time.ntp)