PageRenderTime 34ms CodeModel.GetById 30ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

#! | 50 lines | 38 code | 12 blank | 0 comment | 0 complexity | fc6c9baa60da30541d0c99ac96b22dd3 MD5 | raw file
Possible License(s): MPL-2.0-no-copyleft-exception, BSD-3-Clause, LGPL-2.0, LGPL-2.1, BSD-2-Clause, 0BSD, JSON, AGPL-1.0, GPL-2.0
 1HP e3000 MPE/iX NTP Hints - May 29, 2001
 4NTP was first ported to MPE several years ago, but those diffs were never
 5submitted back to the official NTP distribution.  For more information about
 6that deprecated port, please see
 8NTP was re-ported to MPE in May 2001.  What follows are hints learned from
 9working with NTP 4.0.99k23.  For additional information about NTP on MPE,
10please see
12MPE lacks the clock-related APIs expected by NTP, so adjtime(), gettimeofday(),
13and settimeofday() all had to be implemented from scratch by calling
14privileged, undocumented internal OS functions.
16Unfortunately the implementation of adjtime() has exposed a sub-second accuracy
17bug when slewing the system time.  This bug is documented in SR 5003462838, and
18exists on all current versions of MPE.  It has not been fixed at the time of
19this writing.  The adjtime() code may possibly need to be altered if/when this
20bug is fixed.
22This bug has a side-effect whereby the ntpd daemon will screw up the hardware
23PDC clock time by many minutes if used for continuous clock adjustments or in
24the one-time -q mode.  But note that you can safely run ntpd in order to become
25a time server if you include "disable ntp" in the ntp.conf configuration file.
27The one-time clock adjustment functionality of ntpdate and ntp_timeset is not
28affected by this bug side-effect.  You can safely use these commands to alter
29your system time with reasonable accuracy.
31The only reference clock that has been tested on MPE is the local clock.  So
32building NTP with --disable-all-clocks --enable-LOCAL_CLOCK is strongly
35NTP makes use of Privileged Mode (PM) capability in order to bind to the NTP
36network port (123) and to access the low-level clock functions.
38NTP was ported using the gcc compiler.  Attempting to use the HP C/iX compiler
39is not recommended and has not been tested.
41Please note that NTP is not an HP product and is NOT supported by HP.  The best
42place for asking MPE-specific questions about NTP is the HP3000-L mailing list
43at or the associated Usenet
44newsgroup of comp.sys.hp.mpe.
46The original author of this port is:
48Mark Bixby
49HP CSY MPE Internet & Interoperability Engineer