Re: Strange dates with ntpd

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        hello.  Is it possible you have a mismatch between kernel and
userland?  That looks like something you might see if one thinks it's using
a 32 bit time_t while the other is using a 64 bit time_t.  I realize you're
running a 64-bit version of NetBSD, but I'm not sure when the time
subsystems were converted to use all 64-bit time_t.

-Brian

On Aug 30,  7:58am, Julian Coleman wrote:
} Subject: Strange dates with ntpd
} Hi,
} 
} Has anyone else seen ntpd not set the time correctly?  For example:
} 
}  # date
}  Sat Apr 19 20:03:55 BST 10859
} 
} when the peerings look OK:
} 
}  ntpq> pe
}       remote           refid      st t when poll reach   delay   offset  
jitter
}  
==============================================================================
}  +stratum-2-core- 129.7.1.66       2 u   58   64  377  134.192   -2.756   
0.121
}  *ntppub.le.ac.uk 140.203.204.77   2 u   28   64  377   27.818   -3.635   
1.175
}  -anor.coris.org. 96.223.71.249    3 u   16   64  377    0.316  -19.739   
0.221
}  +orthanc.coris.o 61.69.233.69     3 u    6   64  377    0.365   -3.968   
0.074
} 
} This is a sparc64 running 6.99.10.  I'd replaced the system board, so the
} clock almost certainly contained the wrong time.  At startup, it ran ntpdate
} before ntpd.  /var/log/messages contains:
} 
}   Apr 19 10:52:22 orion -: 10859-04-19T10:52:31.361110+01:00 
orion.coris.org.uk ntpdate 181 - - step time server 91.121.48.21 offset 
-0.316913 sec
} 
} I ran `rdate <remote>` while ntpq was still running, the time was set to
} 2012, and ntpd continued to run (it showed a jump in the offset (to 640ms)
} and jitter for all the peers).
} 
} Thanks,
} 
} J
} 
} PS.  Real date was approximately Aug 30 07:26 BST at this point.
} 
} -- 
}    NetBSD: simple; works; documented    /        Sailing at Newbiggin
}         http://www.netbsd.org/        /   http://www.newbigginsailingclub.org/
>-- End of excerpt from Julian Coleman