| It's typically about +/- 1 min per month. We don't test it or guarantee
a specific limit. Also note that OS sometimes will lose ticks because of driver
bugs (too long at high IPL, etc.) and this can further degrade accuracy. For
accurate long-term timekeeping, you should use an internet time reference or
cesium clock, etc.
--RS
|
|
This question has been asked (and answered) a number of times before.
See note 530.2 in WRKSYS::MIKASA, and VAXAXP::NOTES$ARCHIVE:ALPHANOTES_V2
notes 48.* and 730.*, and particularly 48.6, for the BB_WATCH (TOY) clock.
The interval clock drift is specified as 50 ppm or better, for the OpenVMS
PALcode. See ALPHANOTES_V2 notes 172.*, TURRIS::DIGITAL_UNIX 185.*, etc.
I suspect this will be the minimum for NT and UNIX as well, and that the
actual drift will be less than this.
Be aware that the tick size calculation can vary. See ALPHANOTES_V1, note
564.8, among others.
There are other discussions. See http://altavista.notes.lkg.dec.com:8000/.
|