Loading ...
Sorry, an error occurred while loading the content.

Re: Ntp

Expand Messages
  • maverik044
    Oddly enough the time is right, right now. I uninstalled the package, installed ntpclient, uninstalled ntpclient, then installed ntp to get the following:
    Message 1 of 6 , Dec 31, 2004
    • 0 Attachment
      Oddly enough the time is right, right now. I uninstalled the
      package, installed ntpclient, uninstalled ntpclient, then installed
      ntp to get the following:

      This is for 0.pool.ntp.org
      31 Dec 20:35:26 ntpdate[1430]: adjust time server 66.111.46.200
      offset 0.075187 sec
      31 Dec 20:35:49 ntpdate[1432]: adjust time server 140.192.21.130
      offset 0.357365 sec
      31 Dec 20:58:49 ntpdate[1454]: step time server 212.79.244.34 offset
      0.581395 sec
      31 Dec 21:05:19 ntpdate[1455]: step time server 195.71.86.233 offset
      3.773242 sec


      time.nrc.ca
      31 Dec 20:37:21 ntpdate[1433]: step time server 132.246.168.148
      offset 1.139684 sec
      31 Dec 20:57:48 ntpdate[1452]: step time server 132.246.168.164
      offset 11.896307 sec
      31 Dec 20:58:33 ntpdate[1453]: adjust time server 132.246.168.164
      offset 0.448963 sec
      31 Dec 21:05:30 ntpdate[1456]: adjust time server 132.246.168.164
      offset 0.132328 sec

      Using ntpq -q
      ntpq -p
      remote refid st t when poll reach delay
      offset jitter
      =====================================================================
      =========
      gusi.leathercol 209.81.9.7 2 u 13 64 1 327.430
      324.059 0.061
      81-174-11-4.f5. 195.113.144.201 2 u 12 64 1 143.400
      323.362 0.061
      ntp1.chorus.net .GPS. 1 u 11 64 1 30.039
      337.477 0.061

      ntpq -p
      remote refid st t when poll reach delay
      offset jitter
      =====================================================================
      =========
      gusi.leathercol 209.81.9.7 2 u 30 64 3 327.430
      324.059 599.374
      81-174-11-4.f5. 195.113.144.201 2 u 30 64 3 143.400
      323.362 591.689
      ntp1.chorus.net .GPS. 1 u 28 64 3 30.039
      337.477 596.739


      remote refid st t when poll reach delay
      offset jitter
      =====================================================================
      =========
      time.nrc.ca 132.246.168.9 2 u 23 64 1 13.680
      2050.09 0.061

      remote refid st t when poll reach delay
      offset jitter
      =====================================================================
      =========
      time.nrc.ca 132.246.168.9 2 u 42 64 3 12.474
      2630.64 580.548


      --- In nslu2-linux@yahoogroups.com, Lennert Buytenhek <buytenh@w...>
      wrote:
      > On Thu, Dec 30, 2004 at 11:23:10PM -0000, maverik044 wrote:
      >
      > > I've installed ntp 4.2.0, it does seem to be pulling the time
      from
      > > an ntp server (in my case time.nrc.ca), but its off by 5-8
      minutes.
      > > I've looked at
      http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html
      > > and haven't found anything that explains it. Also tried
      > > time.nist.gov, samething. Any suggestions?
      >
      > I had this problem because I was using hardfloat and the kernel
      floating
      > point emulator was not emulating the mnfd ('negate') opcode
      correctly.
      > ntp ended up adjusting the system time the wrong way because it
      thought
      > that -1.0 = 1.0!
      >
      > What does 'ntpdate time.nrc.ca' give for 'offset' (stop ntpd while
      you
      > do this)? What if you run it a few times in a row? And spaced
      apart by
      > a few minutes?
      >
      >
      > --L
    • maverik044
      Now its off by 12 minutes ntpq -p remote refid st t when poll reach delay offset jitter
      Message 2 of 6 , Jan 1, 2005
      • 0 Attachment
        Now its off by 12 minutes

        ntpq -p
        remote refid st t when poll reach delay
        offset jitter
        =====================================================================
        =========
        time.nrc.ca 132.246.168.9 2 u 176 1024 377 19.339
        707870. 9946.39


        --- In nslu2-linux@yahoogroups.com, "maverik044" <maverik044@y...>
        wrote:
        >
        > Oddly enough the time is right, right now. I uninstalled the
        > package, installed ntpclient, uninstalled ntpclient, then
        installed
        > ntp to get the following:
        >
        > This is for 0.pool.ntp.org
        > 31 Dec 20:35:26 ntpdate[1430]: adjust time server 66.111.46.200
        > offset 0.075187 sec
        > 31 Dec 20:35:49 ntpdate[1432]: adjust time server 140.192.21.130
        > offset 0.357365 sec
        > 31 Dec 20:58:49 ntpdate[1454]: step time server 212.79.244.34
        offset
        > 0.581395 sec
        > 31 Dec 21:05:19 ntpdate[1455]: step time server 195.71.86.233
        offset
        > 3.773242 sec
        >
        >
        > time.nrc.ca
        > 31 Dec 20:37:21 ntpdate[1433]: step time server 132.246.168.148
        > offset 1.139684 sec
        > 31 Dec 20:57:48 ntpdate[1452]: step time server 132.246.168.164
        > offset 11.896307 sec
        > 31 Dec 20:58:33 ntpdate[1453]: adjust time server 132.246.168.164
        > offset 0.448963 sec
        > 31 Dec 21:05:30 ntpdate[1456]: adjust time server 132.246.168.164
        > offset 0.132328 sec
        >
        > Using ntpq -q
        > ntpq -p
        > remote refid st t when poll reach delay
        > offset jitter
        >
        =====================================================================
        > =========
        > gusi.leathercol 209.81.9.7 2 u 13 64 1 327.430
        > 324.059 0.061
        > 81-174-11-4.f5. 195.113.144.201 2 u 12 64 1 143.400
        > 323.362 0.061
        > ntp1.chorus.net .GPS. 1 u 11 64 1 30.039
        > 337.477 0.061
        >
        > ntpq -p
        > remote refid st t when poll reach delay
        > offset jitter
        >
        =====================================================================
        > =========
        > gusi.leathercol 209.81.9.7 2 u 30 64 3 327.430
        > 324.059 599.374
        > 81-174-11-4.f5. 195.113.144.201 2 u 30 64 3 143.400
        > 323.362 591.689
        > ntp1.chorus.net .GPS. 1 u 28 64 3 30.039
        > 337.477 596.739
        >
        >
        > remote refid st t when poll reach delay
        > offset jitter
        >
        =====================================================================
        > =========
        > time.nrc.ca 132.246.168.9 2 u 23 64 1 13.680
        > 2050.09 0.061
        >
        > remote refid st t when poll reach delay
        > offset jitter
        >
        =====================================================================
        > =========
        > time.nrc.ca 132.246.168.9 2 u 42 64 3 12.474
        > 2630.64 580.548
        >
        >
        > --- In nslu2-linux@yahoogroups.com, Lennert Buytenhek
        <buytenh@w...>
        > wrote:
        > > On Thu, Dec 30, 2004 at 11:23:10PM -0000, maverik044 wrote:
        > >
        > > > I've installed ntp 4.2.0, it does seem to be pulling the time
        > from
        > > > an ntp server (in my case time.nrc.ca), but its off by 5-8
        > minutes.
        > > > I've looked at
        > http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html
        > > > and haven't found anything that explains it. Also tried
        > > > time.nist.gov, samething. Any suggestions?
        > >
        > > I had this problem because I was using hardfloat and the kernel
        > floating
        > > point emulator was not emulating the mnfd ('negate') opcode
        > correctly.
        > > ntp ended up adjusting the system time the wrong way because it
        > thought
        > > that -1.0 = 1.0!
        > >
        > > What does 'ntpdate time.nrc.ca' give for 'offset' (stop ntpd
        while
        > you
        > > do this)? What if you run it a few times in a row? And spaced
        > apart by
        > > a few minutes?
        > >
        > >
        > > --L
      • Lennert Buytenhek
        ... Can you compile this and run it? #include #include int main() { volatile double x; volatile double y; x = 0.5; y = -x; printf( -0.5 =
        Message 3 of 6 , Jan 2, 2005
        • 0 Attachment
          On Sat, Jan 01, 2005 at 10:25:15PM -0000, maverik044 wrote:

          > Now its off by 12 minutes

          Can you compile this and run it?

          #include <stdio.h>
          #include <stdlib.h>

          int main()
          {
          volatile double x;
          volatile double y;

          x = 0.5;
          y = -x;
          printf("-0.5 = %f\n", y);

          return 0;
          }


          --L
        • maverik044
          Didn t try what you suggested below, but I have upgraded to 3.17, which is suppose to have the floating point bug fix, but ntp still does not maintain the
          Message 4 of 6 , Jan 11, 2005
          • 0 Attachment
            Didn't try what you suggested below, but I have upgraded to 3.17,
            which is suppose to have the floating point bug fix, but ntp still
            does not maintain the correct time.

            I'm going to try ntpclient instead.

            --- In nslu2-linux@yahoogroups.com, Lennert Buytenhek <buytenh@w...>
            wrote:
            > On Sat, Jan 01, 2005 at 10:25:15PM -0000, maverik044 wrote:
            >
            > > Now its off by 12 minutes
            >
            > Can you compile this and run it?
            >
            > #include <stdio.h>
            > #include <stdlib.h>
            >
            > int main()
            > {
            > volatile double x;
            > volatile double y;
            >
            > x = 0.5;
            > y = -x;
            > printf("-0.5 = %f\n", y);
            >
            > return 0;
            > }
            >
            >
            > --L
          Your message has been successfully submitted and would be delivered to recipients shortly.