diff options
Diffstat (limited to 'html/hints')
| -rw-r--r-- | html/hints/a-ux | 195 | ||||
| -rw-r--r-- | html/hints/aix | 76 | ||||
| -rw-r--r-- | html/hints/bsdi | 65 | ||||
| -rw-r--r-- | html/hints/changes | 13 | ||||
| -rw-r--r-- | html/hints/decosf1 | 40 | ||||
| -rw-r--r-- | html/hints/decosf2 | 54 | ||||
| -rw-r--r-- | html/hints/freebsd | 15 | ||||
| -rw-r--r-- | html/hints/hpux | 158 | ||||
| -rw-r--r-- | html/hints/linux | 5 | ||||
| -rw-r--r-- | html/hints/mpeix | 50 | ||||
| -rw-r--r-- | html/hints/notes-xntp-v3 | 119 | ||||
| -rw-r--r-- | html/hints/parse | 105 | ||||
| -rw-r--r-- | html/hints/refclocks | 35 | ||||
| -rw-r--r-- | html/hints/rs6000 | 56 | ||||
| -rw-r--r-- | html/hints/sco.html | 29 | ||||
| -rw-r--r-- | html/hints/sgi | 74 | ||||
| -rw-r--r-- | html/hints/solaris-dosynctodr.html | 321 | ||||
| -rw-r--r-- | html/hints/solaris.html | 236 | ||||
| -rw-r--r-- | html/hints/solaris.xtra.4023118 | 36 | ||||
| -rw-r--r-- | html/hints/solaris.xtra.4095849 | 74 | ||||
| -rw-r--r-- | html/hints/solaris.xtra.S99ntpd | 21 | ||||
| -rw-r--r-- | html/hints/solaris.xtra.patchfreq | 85 | ||||
| -rw-r--r-- | html/hints/sun4 | 15 | ||||
| -rw-r--r-- | html/hints/svr4-dell | 8 | ||||
| -rw-r--r-- | html/hints/svr4_package | 33 | ||||
| -rw-r--r-- | html/hints/todo | 4 | ||||
| -rw-r--r-- | html/hints/vxworks.html | 88 | ||||
| -rw-r--r-- | html/hints/winnt.html | 90 |
28 files changed, 2100 insertions, 0 deletions
diff --git a/html/hints/a-ux b/html/hints/a-ux new file mode 100644 index 0000000..f8c26d2 --- /dev/null +++ b/html/hints/a-ux @@ -0,0 +1,195 @@ +------------- +INTRODUCTION: +------------- +Last revision: 06-Jul-1994 + +Included in this distribution of XNTP V3 is a configuration file suitable +for use under Apple's A/UX Version 3.x.x There is also one for A/UX 2.0.1 +but it has not been fully tested. To make the executables follow the steps +outlined below. + +*** NOTE: You must have gcc installed to successfully compile the current +distribution; the native cc supplied with A/UX will NOT correctly compile +this source. See the FAQ in comp.unix.aux for places to obtain gcc from +and how to install it. + +---------------------- +MAKING XNTPD FOR A/UX: +---------------------- + +First, you need to create the makefiles (after you've downloaded the +source, of course): + + % make clean + % make refconf + +After that, you should edit Config.local to make sure that BINDIR is +correct for where you wish the programs to be "installed". The default +(and what I use) is /usr/local/etc. Make sure that DEFS_LOCAL and +CLOCKDEFS are commented out! Presently, only the LOCAL_CLOCK/REFCLOCK +clock is used and supported. + + +After this is done (you should be told that your system is A/UX 3), make +'xntpd' (the options to 'gcc' are held in compilers/aux3.gcc): + + % make + +I do not normally use the `make install' option and so have not verified its +compatibility with A/UX. Rather, I pull out each of the executables and +place them in the locally appropriate locations. + +--------------- +STARTING XNTPD: +--------------- + +At this point you need to set things up so that 'xntpd' is started upon +boot-up. You can do this in 1 of 2 ways: either add entries in /etc/inittab +or, more ideally, create and use an /etc/rc.local file. Since rc.local is +what I recommend, here's how you do it: + +By default, A/UX doesn't have rc.local, so you'll need to add the following to +/etc/inittab: + + net6:2:wait:/etc/syslogd # set to "wait" to run a syslog daemon ++ jmj0:2:wait:/etc/rc.local 1>/dev/syscon 2>&1 # Local stuff + dbg2::wait:/etc/telinit v # turn off init's verbose mode + +Now, the look of a sample /etc/rc.local is as follows: + + #!/bin/sh + : + : rc.local + : + # @(#)Copyright Apple Computer 1987 Version 1.17 of rc.sh on 91/11/08 15:56:21 (ATT 1.12) + + + # Push line discipline/set the device so it will print + /etc/line_sane 1 + echo " " + echo "Entering rc.local..." + + set `/bin/who -r` + if [ "$7" = 2 ] + then + /bin/echo " now setting the time..." + /usr/local/etc/ntpdate -s -b <host.domain> + sleep 5 + # + # start up 'xntpd' if we want + # + if [ -f /etc/ntp.conf ] + then + /bin/echo " setting tick and tickadj..." + /usr/local/etc/tickadj -t 16672 -a 54 + sleep 5 + /bin/echo " starting xntpd..." + /usr/local/etc/xntpd <&- > /dev/null 2>&1 + sleep 5 + fi + # + fi + + echo "Leaving rc.local..." + +There are a few things to notice about the above: + + o When run, 'ntpdate' forces your clock to the time returned by the + host(s) specified by <host.domain> (you'll need to replace this + be the IP address(es) of your timehosts. This is good since it gets + things close to start off with. You can use more than one time + server. + + o 'tickadj' is also called. This does two things: changes the + default value of 'tick' (which the the amount of time, in ms, that + is added to the clock every 1/60 seconds) and changes the value + of 'tickadj' which the the amount that is added or subtracted + from 'tickadj' when adjtime() is called. + + Now Mac clocks are pretty bad and tend to be slow. Sooo, instead of + having A/UX add the default of 16666ms every 1/60th of a second, you + may want it to add more (or less) so that it keeps better time. The + above value works for me but your "best" value may be different and + will likely require some fooling around to find the best value. As a + general rule of thumb, if you see 'xntpd' make a lot of negative clock + adjustments, then your clock is fast and you'll need to _decrease_ + the value of 'tick'. If your adjustments are positive, then you need + to increase 'tick'. To make a guess on how fast/slow your clock is, + use 'ntpdate' to sync your clock. Now watch 'xntpd' and see how it + operates. If, for example, it resets your clock by 1 second every 30 + minutes, then your clock is (1/(30*60)) is about 0.056% off and you'll + need to adjust 'tick' by 16666*0.00056 or about 9 (i.e. 'tick' should + be ~16675 if slow or ~16657 if fast) + + A/UX's default value of 'tickadj' is 1666 which is too big for + 'xntpd'... so it also needs to be adjusted. I like using larger + values then the recommended value of 9 for 'tickadj' (although not + anything near as big as 1666) since this allows for quick slews + when adjusting the clock. Even with semi-large values of 'tickadj' + (~200), getting 5ms (1/200 s) accuracy is easy. + + +Finally, before A/UX and 'xntpd' will work happily together, you need to +patch the kernel. This is due to the fact that A/UX attempts to keep the +UNIX-software clock and the Mac-hardware clock in sync. Neither the h/w or +the s/w clock are too accurate. Also, 'xntpd' will be attempting to adjust +the software clock as well, so having A/UX muck around with it is asking +for headaches. What you therefore need to do is tell the kernel _not_ to +sync the s/w clock with the h/w one. This is done using 'adb'. The +following is a shell script that will do the patch for you: + + #! /bin/sh + adb -w /unix <<! + init_time_fix_timeout?4i + init_time_fix_timeout?w 0x4e75 + init_time_fix_timeout?4i + $q + ! + +This must be done _every_ time you create a new kernel (via newconfig or +newunix) or else 'xntpd' will go crazy. + +-------- +HISTORY: +-------- + +John Dundas was the original porter of 'xntpd' and a lot of the additions +and A/UX-ports are from him. I got involved when I wanted to run 'xntpd' +on jagubox. It was also around this time that the base-patchlevel of +'xntpd' changed relatively (the so-called "jones" version). Since then, +I've been maintaining 'xntpd' for A/UX for the xntp development team + +The original kernel patch (which patched 'time_fix_timeout') was from +Richard Todd. I suggest patching 'init_time_fix_timeout' which prevents +'time_fix_timeout' from even being called. + +---------------- +TECHNICAL NOTES: +---------------- + + o As configured (see machines/aux3), 'xntpd' will log messages via syslogd + using the LOC_LOCAL1 facility. I would suggest the following in + /etc/syslog.conf: + + local1.notice /usr/adm/ntpd-syslog + + o As mentioned above, the clocks on A/UX and Macs are kinda bad. Not + only that, but logging in and out of the MacOS mode as well as + extensive floppy use causes A/UX to drop and lose clock interupts + (these are sent every 1/60th of a second). So, if you do these + activities a lot, you find out that you lose about 300ms of time + (i.e., you become 300ms slow). 'xntpd' default way of handling this + is to called 'settimeofday()' and step the clock to the correct + time. I prefer having 'xntpd' slew the clock back into line by + making gradual adjustments to the clock over a coupla minutes + or so. It's for this reason that SLEWALWAYS is defined in + include/ntp_machine.h for SYS_AUX3. It's also for this reason than + I like larger values of 'tickadj'. + +Good luck! If you have problems under A/UX feel free to contact me (e-mail +is preferred). +-- + Jim Jagielski | "That is no ordinary rabbit... 'tis the + jim@jagubox.gsfc.nasa.gov | most foul, cruel and bad-tempered + NASA/GSFC, Code 734.4 | rodent you ever set eyes on" + Greenbelt, MD 20771 | Tim the Enchanter diff --git a/html/hints/aix b/html/hints/aix new file mode 100644 index 0000000..e53beff --- /dev/null +++ b/html/hints/aix @@ -0,0 +1,76 @@ +Problem with recent ANSI compilers + +On some systems, including AIX, the compiler quits on the ntp_refclock.c +file when processing the refclock_report() routine. The problem, which +is eithre a feature or a bug, has to do with an unwanted promotion of +the u_char argument to an int and a failure of the compiler to recognize +the preceding prototype. A workaround is to use ANSI syntax to delare +the arguments. Since ANSI compilers are not universally available, this +syntax can't be used in the stock distribution. + +(Message # 60: 2884 bytes, New) +Date: Sat, 19 Aug 1995 13:20:50 -0400 +From: "R. Bernstein" <rocky@panix.com> +Newsgroups: comp.protocols.time.ntp +to: mills@udel.edu +return-receipt-to: rocky@panix.com +Subject: time and AIX 3.2.5 raw tty bug + +This posting isn't strictly about NTP, any program that may stop the +clock or set the clock backwards is subject to the AIX 3.2.5 bug. + +On AIX 3.2.5, there is a bug in the tty driver for a raw device which +may crash the box under certain conditions: basically a read() on a +raw tty in effect, a character was read but not as many as specified +by VMIN when a read timeout occurred. VTIME specifies the timeout. See +the AIX manual page on termios.h or that include file. for Information +on VMIN (or MIN) VTIME (or TIME). + +A remedy other than to not use raw tty's is to apply patch U435110. + +Details of the problem report follow. + +> ABSTRACT: +> IX43779: TRAP IN PSX_TIMEO +> +> ORIGINATING DETAILS: +> Stacktrace shows: +> IAR: 01460214 posixdd:psx_timeo + 8bf4: ti 4,r12,0x0 +> *LR: 014601a0 posixdd:psx_timeo + 8b80 +> 00212c60: 014604f4 posixdd:psx_timer + 8ed4 +> 00212cc0: 0144b74c ttydd:tty_do_offlevel + 4284 +> 00212d20: 000216fc .i_offlevel + 8c +> 00212d70: 00021d78 .i_softint + c8 +> 00001004: 00008714 .finish_interrupt + 80 +> +> RESPONDER SUMMARY: +> AIX asserted in psx_timeo(). Reason for the assert was that +> the current time was behind psx_ctime. Since this state +> can occur when the current time is changed after a character +> is received but before the VTIME interbyte timer pops, we +> should not assert on this. +> +> RESPONDER CONCLUSION: +> Removed the requirement that current time > psx_ctime by +> adding a new L_ntimersub macro that is used instead of the +> ntimersub macro in time.h. Also added a test for (current +> time - psx_ctime) being negative, in that case we do not +> adjust the new timeout. +> +> Reported to Correct a PTF in Error: NO +> Reported as a Highly pervasive problem: NO +> +> PE Apar?: NoPE +> Hiper Apar?: NoHiper +> Status: CLOSED PER +> Component Name: AIX V3 FOR RS/6 +> Version: 320 +> Component ID: 575603001 +> Submitted: 94/05/03 +> Closed: 94/05/05 +> ChangeTeam: TX2527 +> +> APAR FIXED BY: U431696 U432151 U432844 U432870 U432979 +> U433049 U433081 U433459 U433876 U433906 U434598 U434453 +> U434672 U434737 U435110 + diff --git a/html/hints/bsdi b/html/hints/bsdi new file mode 100644 index 0000000..3b8bc38 --- /dev/null +++ b/html/hints/bsdi @@ -0,0 +1,65 @@ +hints/bsdi + +Author: Bdale Garbee, bdale@gag.com +Last revision: 27Oct94 (Paul Vixie) + +Included in this distribution of XNTP is a configuration file suitable +for use with BSDI's BSD/OS 1.1 (formerly BSD/386 1.1). On this system, +the "cc" command is GCC 1.4x rather than PCC or GCC 2.x. It is imperative +that "cc" be used since it predefines the symbol __bsdi__; if you want to +use another compiler you will need to add -D__bsdi__ to catch the various +#ifdef's required for this system. + +The Kinemetrics/Truetime GPS-TM/TMD driver is known to work on this system. +The GPS-805 and GOES should also work fine. Hell, they should all work fine +but it's hard to test very many locally. + +Due to BNR2's strict interpretation of POSIX and XNTP's use of SIGIO, BSD/OS +can only handle one refclock per daemon. We're working this out with the +system architects. + +The config file is machine/bsdi, and the following steps should be all that +are required to install and use the bits. + +Note that you will need GNU sed; the version supplied with BSD/OS 1.1 loops +endlessly during "make refconf". Likewise you should get GNU make, which +the instructions below assume that you have put in /usr/local/bin/gnumake. + +To build the software: + + rm -f Config.local + gnumake refconf + gnumake MAKE=gnumake + +To install the software: + + gnumake install + + This will place all of the executables in /usr/local/etc. The config + file is expected to be /usr/local/etc/xntp.conf and the key file for + the optional authentication is /etc/ntp.keys. + + Craft a config file and a key file, and put them in the right places. + There is information on how to do this elsewhere in the documentation, + the only thing I'll mention is that I put the drift file in + /var/log/ntp.drift, and the authdelay on my 486DX/50 system is + 0.000064. Your mileage will vary, learn to use the authspeed tools + if you're going to authenticate. + + In the file /etc/rc.local, make sure that the invocation of ntpd is + commented out, and add an invocation of xntpd. Here's what I'm using: + + echo -n 'starting local daemons:' + + if [ -f /etc/ntp.keys -a -f /usr/local/etc/xntp.conf ]; then + echo -n ' xntpd'; /usr/local/etc/xntpd + fi + + #XXX# echo -n ' ntpd'; /usr/libexec/ntpd -t + +At this point, you should be good to go. Try running /usr/local/etc/xntpd and +using ntpq or xntpdc to see if things are working, then pay attention the next +time you reboot to make sure that xntpd is being invoked, and use ntpq or +xntpdc again to make sure all is well. + +Enjoy! diff --git a/html/hints/changes b/html/hints/changes new file mode 100644 index 0000000..177e562 --- /dev/null +++ b/html/hints/changes @@ -0,0 +1,13 @@ +Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> (xntpd/refclock_parse.c): + - Added support to supply power from RS232 with CLOCK_RAWDCF. + Known to work with Linux 1.2. + - Made Linux ignore parity errors with CLOCK_RAWDCF. + +Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> (parse/util/dcfd.c): + - Removed conflicting prototype for Linux (sscanf) + - Corrected spelling error + - Made Linux ignore parity errors. + - Added support to supply power from RS232 with CLOCK_RAWDCF. + +Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> (parse/util/testdcf.c): + - Made Linux ignore parity errors. diff --git a/html/hints/decosf1 b/html/hints/decosf1 new file mode 100644 index 0000000..bc4ce0b --- /dev/null +++ b/html/hints/decosf1 @@ -0,0 +1,40 @@ +Some major changes were necessary to make xntp v3 run on the DEC Alpha +hardware running DEC OSF/1. All "long" and "u_long" declarations and +casts in the code were changed to "LONG" and "U_LONG" and a new header +file (include/ntp_types.h) was added. The new header file defines +LONG as int and U_LONG as u_int for the Alpha hardware and as long +and u_long for anything else. A couple of #ifs where changed in +ntpq and xntpdc to get the result of a signal defined correctly. The +Config.decosf1 file built the programs here with no problems. + +I don't have a radio clock here, so none of that code has been tested. +I have run xntpd, xntpdc, xntpres, ntpq, ntpdate, and tickadj under +DEC OSF/1 v1.2-2 (BL10). + +Mike Iglesias Internet: iglesias@draco.acs.uci.edu +University of California, Irvine BITNET: iglesias@uci +Office of Academic Computing uucp: ...!ucbvax!ucivax!iglesias +Distributed Computing Support phone: (714) 856-6926 + +Support for NTP Version 2 is included with the current OSF/1 release. If +you are upgrading to NTP Version 3 with this distribution, you should not +use the xntpd or ntpq programs that come with the OSF/1 release. The +older programs should be replaced by the newer programs of the same name, +either in situ or via a link to a tranquil spot like /usr/local/bin. The +make install script in the this distribution don't work due to a silly +install program incompatibility, so you will need to copy the programs by +hand. + +Don't use the setup utility to install or configure the xntpd installation, +as it will cheerfully clobber your painstakingly crafted ntp.conf program. +However, assuming you put this file in /etc/ntp.conf, you can use the +/sbin/init.d/xntpd script to start and stop the daemon. + +This distribution compiles with nominal mumur with the stock cc compiler +that comes with OSF/1. + +Dave Mills +Electrical Engineering Department +Unibergisty of Delabunch +mills@udel.edu + diff --git a/html/hints/decosf2 b/html/hints/decosf2 new file mode 100644 index 0000000..e4a8828 --- /dev/null +++ b/html/hints/decosf2 @@ -0,0 +1,54 @@ +Problems with DEC OSF/1 V2.0 + +Compilation using gcc fails with ntp_config.c. The problem is an apparent +error in the /usr/include/sys/procset.h and /usr/include/sys/wait.h +include files. + +cowbird:/usr/include/sys# diff -c wait.h.orig wait.h +*** wait.h.orig Tue Feb 22 02:41:38 1994 +--- wait.h Thu Aug 25 14:52:57 1994 +*************** +*** 298,304 **** + #else + + _BEGIN_CPLUSPLUS +! extern int waitid(idtype_t, id_t, siginfo_t *, int); + _END_CPLUSPLUS + #endif /* _NO_PROTO */ + +--- 298,304 ---- + #else + + _BEGIN_CPLUSPLUS +! extern int waitid(idtype_t, pid_t, siginfo_t *, int); + _END_CPLUSPLUS + #endif /* _NO_PROTO */ + +cowbird:/usr/include/sys# diff -c procset.h.orig procset.h +*** procset.h.orig Tue Feb 22 02:41:44 1994 +--- procset.h Thu Aug 25 14:43:52 1994 +*************** +*** 86,95 **** + */ + + idtype_t p_lidtype; /* The id type for the left set. */ +! id_t p_lid; /* The id for the left set. */ + + idtype_t p_ridtype; /* The id type of for right set. */ +! id_t p_rid; /* The id of the right set. */ + } procset_t; + + +--- 86,95 ---- + */ + + idtype_t p_lidtype; /* The id type for the left set. */ +! pid_t p_lid; /* The id for the left set. */ + + idtype_t p_ridtype; /* The id type of for right set. */ +! pid_t p_rid; /* The id of the right set. */ + } procset_t; + +Also, if using gcc from the freeware disk, either replace syscall.h +in the directory /usr/local/lib/gcc-lib/alpha-dec-osf1/2.3.3/include +or replace with a link to /usr/include/sys/syscall.h. diff --git a/html/hints/freebsd b/html/hints/freebsd new file mode 100644 index 0000000..ef84732 --- /dev/null +++ b/html/hints/freebsd @@ -0,0 +1,15 @@ +If you are compiling under FreeBSD and see messages in the syslogs that +indicate that the ntpd process is trying to use unavailable sched_ +calls, it means you are running a kernel that does not have the POSIX +scheduling calls enabled. + +You have two choices: + +- Ignore the messages + +- Generate a new kernel, where the kernel configuration file contains + the lines: + + options "P1003_1B" + options "_KPOSIX_PRIORITY_SCHEDULING" + options "_KPOSIX_VERSION=199309L" diff --git a/html/hints/hpux b/html/hints/hpux new file mode 100644 index 0000000..1640d05 --- /dev/null +++ b/html/hints/hpux @@ -0,0 +1,158 @@ +Last update: Sun Mar 13 15:05:31 PST 1994 + +This file hopefully describes the whatever and however of how to get xntp +running on hpux 7.0 and later s300. s400, s700, and s800. + +First off, all the standard disclaimers hold here ... HP doesn't have anthing +to do with this stuff. I fool with it in my spare time because we use it and +because I like to. We just happen to have a lot of HP machines around here :-) +Xntpd has been in use here for several years and has a fair amount of mileage +on various HP platforms within the company. I can't really guarantee bug fixes +but I'd certainly like to hear about bugs and I won't hestitate to look at +any fixes sent to me. + +Now lets talk OS. If you don't have 7.0 or later, pretty much hang it up now. +This stuff has run here on pretty much everything from 8.0 upward on s300, +s700, and s800. It is known to run on 7.0 s300/s400 but all reports are +from the field and not my personal experience. + +If you are lucky enough to have a s300 or s400 with 9.03, then you no longer +have to worry about adjtimed as HP-UX now has adjtime(2). The rest of you +will have to wait on 10.0 which will have adjtime(2) and a supported though +a bit older version of xntpd. + +Next, let me explain a bit about how this stuff works on HP-UX's that do not +have adjtime(2). The directory adjtime contains libadjtime.a and the adjtimed +daemon. Instead of the adjtime(2) system call, we use a library routine to +talk to adjtimed thru message queues. Adjtimed munges into /dev/kmem and +causes the clock to skew properly as needed. PLEASE NOTE that the adjtime +code provided here is NOT a general replacement for adjtime(2) ... use of +this adjtime(3)/adjtimed(8) other than with xntpd may yield very odd results. + +What to do to get this stuff running ? + + * If you are running an OS less than 10.0 or do not have a s300/s400 + with 9.03 or better + -> cd machines + -> vi hpux + -> (change -DSYS_HPUX=? to match whatever you are running [7,8,9]) + -> cd .. + + * Say "make makeconfig" + + * Say "make", sit back for a few minutes. + + * cd authstuff + * Say "./authcert < certdata" and check the output. Every line should + end with "OK" ... if not, we got trouble. + * Now try "./authspeed auth.samplekeys". What we want to + remember here is the "authentication delay in CPU time" + * cd .. + + * Say "make install" + + * I'd suggest reading the xntp docs about now :-) ... seriously !! + + * One thing I have added to this version of xntpd is a way to select + config files if you are sharing /usr/local thru NFS or whatever. + If the file /usr/local/etc/xntp.conf happens to be a directory, the + files in that directory are searched until a match is found. The + rules for a match are: + + 1. Our hostname + 2. default.<machine id> (as in default.375 or default.850) + 3. default + + * Ok, make sure adjtimed is running (just start it up for now with + "/usr/local/etc/adjtimed"). Using -z as an option will get you + a usage message. + + * Now start up xntpd and watch it work. + + * Make sure that adjtimed gets started at boot right before xntpd. + We do this in /etc/netbsdsrc. They must both run as root !! + +Possible problems ? + + * On some 320's and 835's we have had to run adjtimed with "-p 45" or + so to get rid of syslog messages about "last adjust did not finish". + + * At 9.0, there is a problem with DIAGMON (patch available from the + response center) which causes it to delete the message queue that + adjtimed/xntpd use to communicate. (see next note for result) + + * Xntpd has been known to get really ticked off when adjtime() fails + which is usually only while running the emulation code on HP-UX. + When it gets mad, it usually jumps the clock into never never land. + Possible reasons for this are adjtimed being killed or just never + started or adjtimed being completely swapped out on a really busy + machine (newer adjtimed try to lock themselves in memory to prevent + this one). + +Anything else ... just drop me a line at ken@sdd.hp.com + +Received: from louie.udel.edu by huey.udel.edu id aa14418; 15 Jun 95 9:19 EDT +Received: from host5.colby.edu (host-05.colby.edu) by host-04.colby.edu with ESMTP (1.37.109.15/Colby 1.1) + id AA165442355; Thu, 15 Jun 1995 09:19:16 -0400 +Received: by host5.colby.edu (1.37.109.15/Colby 1.1) + id AA056252339; Thu, 15 Jun 1995 09:18:59 -0400 +Date: Thu, 15 Jun 1995 09:18:59 -0400 (EDT) +From: "Jeff A. Earickson" <jaearick@colby.edu> +To: Mills@huey.udel.edu +Subject: More minor bugs in xntp3.4s +In-Reply-To: <9506150022.aa12727@huey.udel.edu> +Message-Id: <Pine.HPP.3.91.950615083549.4557A-100000@host5.colby.edu> +Mime-Version: 1.0 +Content-Type: TEXT/PLAIN; charset=US-ASCII + +Dave, + After reading the hpux hints file, I realized I didn't install or +start adjtimed. In the course of doing this, I discovered that: + +--> $(TOP) is not defined in adjtime/Makefile, so "make install" can't + find the install.sh script. + +--> "make install" from the main Makefile never goes into the adjtime + directory, so I added the following two lines into the install + target of the main Makefile: + + @echo installing from adjtime + @cd adjtime && $(MAKE) $(MFLAGS) MFLAGS="$(MFLAGS)" MAKE="$(MAKE)" install + +This twiddle may not be right for all systems, but it got adjtimed +installed for me. + + You might also want to add to the hpux hints file that one way to +fire things up at boot time is to add the following lines to the localrc +function of /etc/rc: + + #---daemons for Network Time Protocol (version 3.4s) + #---note that adjtimed is only needed for HP-UX 9.X, not 10.0 + #---adjtimed must be running or xntpd won't work right... + if [ -x /usr/local/bin/adjtimed ]; then + /usr/local/bin/adjtimed -r & echo -n ' adjtimed' + if [ -x /usr/local/bin/xntpd ]; then + /usr/local/bin/xntpd & echo -n ' xntpd' + fi + fi + +I discovered that the "-r" option of adjtimed is needed to clear out any +trash from a previous execution of it. Otherwise adjtimed quietly dies +and leaves xntpd in the lurch... + +Thanks for the help. + +** Jeff A. Earickson, Ph.D PHONE: 207-872-3659 +** Senior UNIX Sysadmin, Information Technology EMAIL: jaearick@colby.edu +** Colby College, 4214 Mayflower Hill, FAX: 207-872-3555 +** Waterville ME, 04901-8842 + +On Thu, 15 Jun 1995 Mills@huey.udel.edu wrote: + +> Jeff, +> +> Read the hpux file in the hints directory. +> +> Dave +> + diff --git a/html/hints/linux b/html/hints/linux new file mode 100644 index 0000000..b06a36a --- /dev/null +++ b/html/hints/linux @@ -0,0 +1,5 @@ +The kernel PLL interface is broken, I know. +Update RSN. + + Torsten + (duwe@informatik.uni-erlangen.de) diff --git a/html/hints/mpeix b/html/hints/mpeix new file mode 100644 index 0000000..83c7241 --- /dev/null +++ b/html/hints/mpeix @@ -0,0 +1,50 @@ +HP e3000 MPE/iX NTP Hints - May 29, 2001 +---------------------------------------- + +NTP was first ported to MPE several years ago, but those diffs were never +submitted back to the official NTP distribution. For more information about +that deprecated port, please see http://www.bixby.org/mark/xntpix.html. + +NTP was re-ported to MPE in May 2001. What follows are hints learned from +working with NTP 4.0.99k23. For additional information about NTP on MPE, +please see http://jazz.external.hp.com/src/hp_freeware/ntp/. + +MPE lacks the clock-related APIs expected by NTP, so adjtime(), gettimeofday(), +and settimeofday() all had to be implemented from scratch by calling +privileged, undocumented internal OS functions. + +Unfortunately the implementation of adjtime() has exposed a sub-second accuracy +bug when slewing the system time. This bug is documented in SR 5003462838, and +exists on all current versions of MPE. It has not been fixed at the time of +this writing. The adjtime() code may possibly need to be altered if/when this +bug is fixed. + +This bug has a side-effect whereby the ntpd daemon will screw up the hardware +PDC clock time by many minutes if used for continuous clock adjustments or in +the one-time -q mode. But note that you can safely run ntpd in order to become +a time server if you include "disable ntp" in the ntp.conf configuration file. + +The one-time clock adjustment functionality of ntpdate and ntp_timeset is not +affected by this bug side-effect. You can safely use these commands to alter +your system time with reasonable accuracy. + +The only reference clock that has been tested on MPE is the local clock. So +building NTP with --disable-all-clocks --enable-LOCAL_CLOCK is strongly +recommended. + +NTP makes use of Privileged Mode (PM) capability in order to bind to the NTP +network port (123) and to access the low-level clock functions. + +NTP was ported using the gcc compiler. Attempting to use the HP C/iX compiler +is not recommended and has not been tested. + +Please note that NTP is not an HP product and is NOT supported by HP. The best +place for asking MPE-specific questions about NTP is the HP3000-L mailing list +at http://raven.utc.edu/Archives/hp3000-l.html or the associated Usenet +newsgroup of comp.sys.hp.mpe. + +The original author of this port is: + +Mark Bixby +HP CSY MPE Internet & Interoperability Engineer +mark_bixby@hp.com diff --git a/html/hints/notes-xntp-v3 b/html/hints/notes-xntp-v3 new file mode 100644 index 0000000..ba027f2 --- /dev/null +++ b/html/hints/notes-xntp-v3 @@ -0,0 +1,119 @@ +Notes for NTP Version 3 + +This version operates in much the same manner as Version 2 with the +following changes and additions: + +1. The protocol machinery operates in conformance with the RFC1305 NTP + Version 3 specification. The most visible characteristic of this + version is that the poll intervals for all polls, even selected + ones, is significantly increased. This is especially desirable when + serving a large client population. This implementation supports + previous versions as non-configured peers; for version-2 configured + peers a "version 2" keyword should be included on the "peer" line. + +2. The configuration file has a new keyword: statfile <file>, where + <file> is the name of a statistics file." When present, each clock + update generates an entry of the form: + + <day> <sec>.<frac> <addr> <status> <offset> <delay> <disp> + + where <day> is the modified Julian day, <sec>.<frac> is the time of + day, <addr> is the peer address and <status> is the peer status. + The <offset>, <delay> and <disp> are the measured offset, delay and + dispersion, respectively, of the peer clock relative to the local + clock. About once per day the current file is closed and a new one + created with names <file>.<gen>, where <gen> starts at one and + increments for each new generation. + +3. A number of additional platforms are supported. See ./Config file + for details. + +4. A driver for the TrueTime 468DC GOES Synchronized Clock is + included. This driver (refclock_goes.c) should also work for other + TrueTime radio clocks, since all use the same format. + +5. A replacement driver for the Spectracom 8170 WWVB Synchronized + Clock is included. This driver (refclock_wwvb.c) (a) does not + require a 1-pulse-per-second signal, (b) supports both format 0 + (original 8170) and format 2 (Netclock/2 and upgraded 8170), (c) + can be connected to more than one computer and (d) automatically + compensates for all serial baud rates. + +6. A driver for the German time/frequency station DCF77 is included. + This requires a special STREAMS module. + +7. In Version 2 special line-discipline modules were required for the + CHU and WWVB drivers. This code continues to work in Version 3, + although it is no longer needed for the WWVB driver. However, this + code does not work under STREAMS, as used in SunOS 4.1.1. + Equivalent STREAMS modules are supplied with Version 3. + +8. Support for an external 1-pulse-per-second (pps) signal is + provided. The signal is connected to a serial port (see + xntpd/ntp_loopfilter.c for details). When present the leading edge + of the pulse establishes the on-time epoch within an interval + established by the selected radio clock or other NTP time server. + Use of the pps is indicated when the tattletale displayed by ntpq + changes from "*" to "o". + +9. The clock-selection and poll-update procedures have been modified + slightly in order to achieve better performance on high speed LANs + with compromise in performance on typical WANs. + +10. In order to comply with U.S. Commerce Department regulations, the DES + encryption routine lib/authdes.c cannot be exported. For exportable + versions of this distribution a DES-encrypted version of this routine + lib/authdes.c.des is included along with an unencrypted version + lib/authdes.c.export, which allows normal operation, but without the + NTP authentication feature. Further information is available in the + lib/authdes.c.export file. + +11. As an alternative to the DES-based authentication mechanism, an + implementation of the RSA Message Digest 5 algorithm is provided. + (see applicable copyright information in the library files). + +12. A driver for the Magnavox MX4200 GPS clock. + +13. A STREAMS module which captures carrier-detect data-lead transitions to + connect a precision source of 1-pps, yet avoid the ugly overhead in the + usual STREAMS processing. See the ppsclock subdirectory. + +14. Support for the Apple A/UX operating system and enhanced support for the + Hewlet-Packard HP/UX operating system. See the various README and Config + files for further information. + +See the COPYRIGHT file for authors and copyright information. Note that some +modules in this distribution contain copyright information that supersedes +the copyright information in that file. + +If I missed something or neglected to give due credit, please advise. + +David L. Mills +University of Delaware +31 May 1992, amended 23 July 1992, 25 October 1992 + +Bugs and notes + +A bug in the original tty_clk_STREAMS.c module has been fixed. + +The poll-interval randomization feature of poll_update (in +xntpd/ntp_proto.c) has been extended to apply when the poll interval is +increased, as well as reduced. This spreads the update messages in time +and helps avoid unpleasant bursts of messages. + +In the clock_select algorithm the peers selected for combining are +limited to those survivors at the lowest stratum, not the entire list. +This helps avoid whiplash when large numbers of peers are at the same +stratum. + +The number formerly displayed by ntpq as "compliance" is now the time +constant of integration. + +The DNS resolver xntpd/ntp_intres.c is now integrated into xntpd, making +configuration of multiple hosts easier. + +System and peer event are now written to the system log at priority +LOG_INFO. + +The leap-second code was fixed to avoid broadcasting leap warnings on +all except the last day of June and December. diff --git a/html/hints/parse b/html/hints/parse new file mode 100644 index 0000000..d252351 --- /dev/null +++ b/html/hints/parse @@ -0,0 +1,105 @@ +Compilation: + Usual thing: rm -f Config.local ; make for vanilla + make refconf for reference clock (e. g. DCF77) + +Directory contents: + + hints/PARSE - this file + + xntpd/refclock_parse.c + - reference clock support for DCF77/GPS in xntp + parse/parse.c + - Reference clock data parser framework + parse/parse_conf.c + - parser configuration (clock types) + parse/clk_meinberg.c + - Meinberg clock formats (DCF U/A 31, PZF 535, GPS166) + parse/clk_schmid.c + - Schmid receiver (DCF77) + parse/clk_rawdcf.c + - 100/200ms pulses via 50 Baud line (DCF77) + parse/clk_dcf7000.c + - ELV DCF7000 (DCF77) + parse/clk_trimble.c + - Trimble SV6 GPS receiver + + If you want to add new clock types please check + with kardel@informatik.uni-erlangen.de. These files + implement the conversion of RS232 data streams into + timing information used by refclock_parse.c which is + mostly generic except for NTP configuration constants. + + parse/Makefile.kernel + - *SIMPLE* makefile to build a loadable STREAMS + module for SunOS 4.x / SunOS 5.x systems + + parse/parsestreams.c + - SUN Streams module (loadable) for radio clocks + This streams module is designed for SunOS 4.1.X. + + parse/parsesolaris.c + - SUN Streams module (loadable) for radio clocks. + This streams module is designed for SunOS 5.x + Beware this is still new - so it might crash + your machine (we have seen it working, though). + + parse/parsetest.c + - simple test program for STREAMS module. Its so simple, + that it doesn't even set TTY-modes, thus they got to + be correct on startup - works for Meinberg receivers + + parse/testdcf.c + - test program for raw DCF77 (100/200ms pulses) + receivers + + include/parse.h - interface to "parse" module and more + include/parse_conf.h + - interface to "parse" configuration + + include/sys/parsestreams.h + - STREAMS specific definitions + + scripts/support + - scripts (perl & sh) for statistics and rc startup + the startup scripts are used in Erlangen for + starting the daemon on a variety of Suns and HPs + and for Reference Clock startup on Suns + These scripts may or may not be helpful to you. + +Supported clocks: + Meinberg DCF U/A 31 + Meinberg PZF535/TCXO (Software revision PZFUERL 4.6) + Meinberg PZF535/OCXO (Software revision PZFUERL 4.6) + Meinberg GPS166 (Software version for Uni-Erlangen) + ELV DCF7000 (not recommended - casual/emergency use only) + Conrad DCF77 receiver (email: time@informatik.uni-erlangen.de) + + level converter + TimeBrick (email: time@informatik.uni-erlangen.de) + Schmid Receiver Kit + Trimble SV6 GPS receiver + +Addresses: + Meinberg Funkuhren + Auf der Landwehr 22 + 31812 Bad Pyrmont + Germany + Tel.: 05281/20 18 + FAX: 05281/60 81 80 + + ELV Kundenservice + Postfach 1000 + 26787 Leer + Germany + Tel.: 0491/60 08 88 + + Walter Schmidt + Eichwisrain 14 + 8634 Hombrechtikon + Switzerland + +If you have problems mail to: + + time@informatik.uni-erlangen.de + +We'll help (conditions permitting) + diff --git a/html/hints/refclocks b/html/hints/refclocks new file mode 100644 index 0000000..17e7643 --- /dev/null +++ b/html/hints/refclocks @@ -0,0 +1,35 @@ +This is a short overview for the reference clocks currently supported +by xntp V3. (Ultimate wisdom can be obtained from xntpd/refclock_*.c +this file was derived from that information - unfortunately some comments +in the files tend to get stale - so use with caution) + +Refclock address Type +127.127.0.x no clock (fails to configure) +127.127.1.x local clock - use local clock as reference +127.127.2.x no clock (fails to configure) +127.127.3.x PSTI 1010/1020 WWV Clock +127.127.4.x SPECTRACOM WWVB receiver 8170 and Netclock/2 +127.127.5.x Kinimetric Truetime 468-DC GOES receiver +127.127.6.x IRIG audio decode (Sun & modified BSD audio driver) +127.127.7.x CHU Timecode (via normal receiver & Bell 103 modem) +127.127.8.x PARSE (generic driver for a bunch of DCF/GPS clocks + can be extended for other clocks too) + 8.0-3 Meinberg PZF535/TCXO + 8.4-7 Meinberg PZF535/OCXO + 8.8-11 Meinberg DCF U/A 31 + 8.12-15 ELV DCF7000 + 8.16-19 Walter Schmid DCF receiver (Kit) + 8.20-23 Conrad DCF77 receiver module + level converter (Kit) + 8.24-27 TimeBrick (limited availability ask + time@informatik.uni-erlangen.de) + 8.28-31 Meinberg GPS166 + 8.32-35 Trimble SV6 GPS receiver +127.127.9.x MX4200 GPS receiver +127.127.10.x Austron 2201A GPS Timing Receiver +127.127.11.x Kinemetrics Truetime OM-DC OMEGA Receiver +127.127.12.x KSI/Odetecs TPRO-S IRIG-B / TPRO-SAT GPS +127.127.13.x Leitch: CSD 5300 Master Clock System Driver +127.127.14.x MSFEES +127/127.15.x TrueTime GPS/TM-TMD +127.127.16.x Bancomm GPS/IRIG Ticktock +127.127.17.x Datum Programmable Time System diff --git a/html/hints/rs6000 b/html/hints/rs6000 new file mode 100644 index 0000000..8561ac2 --- /dev/null +++ b/html/hints/rs6000 @@ -0,0 +1,56 @@ +15.7.1993 +xntp3 compiles now again on AIX. I have disabled prototyping and added +the switch -D_NO_PROTO which disables prototyping in the system include +files. + +Matthias Ernst maer@nmr.lpc.ethz.ch +-------------------------------------------------------------------------------- +Xntp version 3 now support the cc compiler for AIX. +The Config.aix will now use cc by default. You can still compile xntp +with the bsd compiler by changing "COMP= cc" to "COMP= bsdcc" and +and removing the "-DSTUPID_SIGNAL" option from the "DEFS" option. + +xntp and tickadj was also modified so that the value of tickadj is read +form the kernel and can be set by tickadj. For now I would not set +tickadj below 40 us. + +Bill Jones +jones@chpc.utexas.edu +------------------------------------------------------------------------------- + +This is a modified version of xntp version 3 for the RS6000. It works for +AIX 3.2 and these are the same changes as have been applied tothe version 2 +implementation of xntp. It works fine for us but I have not tested all of +the features, especially the local clock support for the RS6000 is not tested +at all. + +Matthias Ernst, ETH-Zuerich, Switzerland - maer@nmr.lpc.ethz.ch + +-------------------------------------------------------------------------------- + +Here the original README.rs6000 for the version 2 implementation: + +A hacked version of xntp for the IBM RS/6000 under AIX 3.1 can be found +in xntp.rs6000.tar.Z. [ if still available at all - Frank Kardel 93/12/3 ] + +This will not work on older versions of AIX due to a kernel bug; to find +out whether you have the kernel bug, compile and run testrs6000.c (see +comments in the code for instructions). + +xntp and testrs6000 require "bsdcc" to compile. This is simply another +entry point into the xlc compiler with various options set for BSD +compatibility. If your system does not have bsdcc, do the following: + +link /bin/bsdcc to /bin/xlc + +put the following into /etc/xlc.cfg: + +* BSD compatibility +bsdcc: use = DEFLT + crt = /lib/crt0.o + mcrt = /lib/mcrt0.o + gcrt = /lib/gcrt0.o + libraries = -lbsd, -lc + proflibs = -L/lib/profiled,-L/usr/lib/profiled + options = -H512,-T512, -qlanglvl=extended, -qnoro, -D_BSD, -D_NONSTD_TYPES, -D_NO_PROTO, -tp,-B/lib/ + diff --git a/html/hints/sco.html b/html/hints/sco.html new file mode 100644 index 0000000..d5d1933 --- /dev/null +++ b/html/hints/sco.html @@ -0,0 +1,29 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> + +<html> + + <head> + <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> + <meta name="generator" content="HTML Tidy, see www.w3.org"> + <title>SCO Unix hints</title> + <link href="../scripts/style.css" type="text/css" rel="stylesheet"> + </head> + + <body> + <h3>SCO Unix hints</h3> +<p>Last update: + <!-- #BeginDate format:En2m -->21-Oct-2010 23:44<!-- #EndDate --> + UTC</p> + <h4>Older SCO Unix versions</h4> + <p>NTP 4.0.x does not run on SCO Unix prior to version 3.2.5.0.0. If you need NTP on an older SCO Unix system and don't mind to modify your kernel, use 3.5.91 which has patches for SCO Unix 3.2.4.x. Apply the kernel modifications as described in <a href="http://www.echelon.nl/en/ntp/sco3-recipe.html">XNTP on SCO 3.2.4.2</a>.</p> + <h4>Compiling NTP</h4> + <p>Delete the old SCO supplied NTP programs using the "custom" utility. Run the NTP configure program with CFLAGS="-b elf -K <i>processor-type</i>" for best results.</p> + <h4>Running NTP</h4> + <p>Run "tickadj -As" after every reboot to set the variables "clock_drift" and "track_rtc" to the right values.</p> + <p>Run "ntpd" with a high negative nice-value, i.e. "nice --19 ntpd" for best results.</p> + <h4>More information</h4> + <p>More information on the way SCO Unix and NTP interact can be found in <a href="http://www.echelon.nl/en/ntp/ntp-on-sco.html">NTP on SCO Unix</a>, which includes links to precompiled versions of NTP.</p> + <p>Kees Hendrikse, January 1999</p> + </body> + +</html> diff --git a/html/hints/sgi b/html/hints/sgi new file mode 100644 index 0000000..5e4f7de --- /dev/null +++ b/html/hints/sgi @@ -0,0 +1,74 @@ +adjtime, tick and tickadj: +-------------------------- + +The SGI value for HZ is 100 under Irix 4, with the system clock running +in nominal mode (ftimer off), so the value for tick is 10000 usec. +Tickadj is a bit more tricky because of the behaviour of adjtime(), +which seems to try to perform the correction over 100-200 seconds, with +a rate limit of 0.04 secs/sec for large corrections. Corrections of +less than 0.017 seconds generally complete in less than a second, +however. + +Some measured rates are as follows: + + Delta Rate (sec/sec) + + > 1 0.04 + 0.75 0.04 + 0.6 0.004 + 0.5 0.004 + 0.4 0.0026 + 0.3 0.0026 + 0.2 0.0013 + 0.1 0.0015 + 0.05 0.0015 + 0.02 0.0003 + 0.01 0.015 +Strange. Anyway, since adjtime will complete adjustments of less than +17msec in less than a second, whether the fast clock is on or off, I +have used a value of 150usec/tick for the tickadj value. + +Fast clock: +----------- + +I get smoother timekeeping if I turn on the fast clock, thereby making +the clock tick at 1kHz rather than 100Hz. With the fast clock off, I +see a sawtooth clock offset with an amplitude of 5msec. With it on, +the amplitude drops to 0.5msec (surprise!). This may be a consequence +of having a local reference clock which spits out the time at exactly +one-second intervals - I am probably seeing sampling aliasing between +that and the machine clock. This may all be irrelevant for machines +without a local reference clock. Fiddling with the fast clock doesn't +seem to compromise the above choices for tick and tickadj. + +I use the "ftimer" program to switch the fast clock on when the system +goes into multiuser mode, but you can set the "fastclock" flag in +/usr/sysgen/master.d/kernel to have it on by default. See ftimer(1). + +timetrim: +--------- + +Irix has a kernel variable called timetrim which adjusts the system +time increment, effectively trimming the clock frequency. Xntpd could +use this rather than adjtime() to do it's frequency trimming, but I +haven't the time to explore this. There is a utility program, +"timetrim", in the util directory which allows manipulation of the +timetrim value in both SGI and xntpd native units. You can fiddle with +default timetrim value in /usr/sysgen/master.d/kernel, but I think +that's ugly. I just use xntpd to figure out the right value for +timetrim for a particular CPU and then set it using "timetrim" when +going to multiuser mode. + +Serial I/O latency: +------------------- + +If you use a local clock on an RS-232 line, look into the kernel +configuration stuff with regard to improving the input latency (check +out /usr/sysgen/master.d/[sduart|cdsio]). I have a Kinemetrics OM-DC +hooked onto /dev/ttyd2 (the second CPU board RS-232 port) on an SGI +Crimson, and setting the duart_rsrv_duration flag to 0 improves things +a bit. + + +12 Jan 93 +Steve Clift, CSIRO Marine Labs, Hobart, Australia (clift@ml.csiro.au) diff --git a/html/hints/solaris-dosynctodr.html b/html/hints/solaris-dosynctodr.html new file mode 100644 index 0000000..89a12b2 --- /dev/null +++ b/html/hints/solaris-dosynctodr.html @@ -0,0 +1,321 @@ + +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + + +<!-- Sun Template V4.0 9/9/98 --> +<HTML> +<HEAD> +<TITLE>Symptoms and Resolutions Article 19195</title><link href="scripts/style.css" type="text/css" rel="stylesheet"> + +<META NAME="GENERATOR" CONTENT="Sun Microsystems, Inc."> +<META HTTP-EQUIV="content-type" CONTENT="text/html;charset=iso-8859-1"> + +<!-- INSERT YOUR META TAGS HERE --> + +<META NAME="PUBLISHED_DATE" CONTENT=""> +<META NAME="KEYWORDS" CONTENT=""> +<META NAME="DESCRIPTION" CONTENT=""> + +<!-- END META TAGS --> + +<LINK REL="Stylesheet" TYPE="text/css" HREF="/style.css" TITLE="Style"> + +</HEAD> +<!--stopindex--> +<BODY BGCOLOR="#FFFFFF" LINK="#666699" ALINK="#FFFFFF"> + + +<TABLE WIDTH="623" BORDER="0" CELLSPACING="0" CELLPADDING="0"> + <TR> + <TD COLSPAN="2" VALIGN="TOP" WIDTH="623"> + <IMG BORDER="0" SRC="/images/homebuy.gif" WIDTH="149" HEIGHT="32" ALT="Home * Buy * My Sun(sm)" USEMAP="#lefttop"><IMG BORDER="0" SRC="/images/globalnavbar.gif" WIDTH="474" HEIGHT="32" ALT="sun.com Global Sections" USEMAP="#topnav"></TD> + </TR> + <TR> + <TD COLSPAN="2" VALIGN="TOP" WIDTH="623"> + + <!-- TITLEBAR IMAGE: INSERT CUSTOMIZED TITLEBAR IMAGE BELOW --> + + <A HREF="http://www.sun.com/"><IMG BORDER="0" SRC="/images/sunlogo.gif" WIDTH="149" HEIGHT="72" ALT="Sun Microsystems"></A><IMG BORDER="0" SRC="/images/titlebar/doc.title.gif" WIDTH="474" HEIGHT="72"></TD> + </TR> + <!-- Begin Search Elements --> + <TR VALIGN="top"> + <TD BGCOLOR="#666699"> + <TABLE BORDER="0" WIDTH="157" CELLSPACING="0" CELLPADDING="0"> + <TR> + <TD BGCOLOR="#666699" COLSPAN="2" WIDTH="157" VALIGN="TOP"><IMG BORDER="0" SRC="/images/search/contract/search1.gif" WIDTH="157" HEIGHT="16" ALT="Search SunSolve"></TD> + </TR> + <TR> + <TD VALIGN="top" ALIGN="center" WIDTH="141" BGCOLOR="#666699"><FORM ACTION="search.pl" METHOD="POST"><FONT SIZE="2"><INPUT TYPE="text" NAME="zone_32" SIZE="14"></FONT><input type=hidden name=mode value=results><BR> +<INPUT TYPE="image" SRC="/images/search/contract/search5.gif" BORDER="0" NAME="Search"><IMG SRC="/images/cg_clear.gif" ALT="" WIDTH="2" HEIGHT="1" BORDER="0" HSPACE="29" VSPACE="0"><BR> + +<A HREF="search.pl?mode=advanced"><IMG BORDER="0" SRC="/images/search/contract/search3.gif" WIDTH="144" HEIGHT="16" ALT="Advanced Search"></A><BR> + +<A HREF="search.pl?mode=product"><IMG SRC="/images/search/contract/search4.gif" BORDER="0" ALT="Product Search" WIDTH="144" HEIGHT="19"></A><BR> + +<A HREF="show.pl?target=help/search_tips"><IMG SRC="/images/search/contract/search6.gif" BORDER="0" ALT="Search Tips" WIDTH="144" HEIGHT="27"></A></TD> + <TD ALIGN="right"><IMG SRC="/images/search/contract/search2.gif" ALT="" WIDTH="13" HEIGHT="117" BORDER="0"></TD> + </TR> + <!-- End Search Elements --> + <!-- Begin User Personalization (Must limit to 10 Characters)--> + <TR> + <TD COLSPAN="2"><TABLE BORDER="0" CELLSPACING="0" CELLPADDING="0" WIDTH="157"><TR><TD COLSPAN="3" ALIGN="right"><IMG SRC="/images/home_con/welcom_1.gif" ALT="" WIDTH="156" HEIGHT="4" BORDER="0"></TD></TR> + <TR><TD BGCOLOR="#333366"><IMG SRC="/images/home_con/welcom_2.gif" ALT="" WIDTH="17" HEIGHT="19" BORDER="0"></TD><TD BGCOLOR="#333366" VALIGN="middle"><NOBR><FONT FACE="Geneva, Helvetica, Arial, SunSans-Regular" COLOR="#99CC33" SIZE="-2">sopko</FONT></NOBR></TD><TD BGCOLOR="#333366" ALIGN="right"><A HREF="edit-user-form.pl?viewmode=contractuser"><IMG SRC="/images/home_con/welcom_3.gif" ALT="Edit" WIDTH="45" HEIGHT="19" BORDER="0"></A></TD></TR> + </TABLE> + </TD> + </TR> + <!-- End User Personalization --> + + <TR> + <TD COLSPAN="2" ALIGN="right" VALIGN="top" WIDTH="157" BGCOLOR="#666699"><IMG BORDER="0" SRC="/images/ssolvecontents.gif" WIDTH="157" HEIGHT="37" ALT="Contents Of SunSolve"><BR> + + + + + + <!-- PILLS: CHANGE THE PILL FOR CURRENT SECTION TO THE HIGHLIGHTED PILL --> + <!-- Beginning of Nav area --> +<A HREF="show.pl?target=patches/patch-access" onmouseover="window.status='All Public Patches'; return true" onmouseout="window.status=''; return true"> +<IMG BORDER="0" SRC="/images/nav/p1.gif" WIDTH="157" HEIGHT="19" ALT="All Public Patches"></A><BR> +<A HREF="suncourier.pl" onmouseover="window.status='Submit a Service Order'; return true" onmouseout="window.status=''; return true"> +<IMG BORDER="0" SRC="/images/nav/p5.gif" WIDTH="157" HEIGHT="19" ALT="Submit a Service Order"></A><BR> +<A HREF="show.pl?target=resources/tools" onmouseover="window.status='Diagnostic Tools'; return true" onmouseout="window.status=''; return true"> +<IMG BORDER="0" SRC="/images/nav/p4.gif" WIDTH="157" HEIGHT="19" ALT="Diagnostic Tools"></A><BR> +<A HREF="show.pl?target=help/collections" onmouseover="window.status='Support Docs.'; return true" onmouseout="window.status=''; return true"> +<IMG BORDER="0" SRC="/images/nav/cp2.gif" WIDTH="157" HEIGHT="19" ALT="Support Docs."></A><BR> +<A HREF="show.pl?target=resources/y2k" onmouseover="window.status='Y2K Central'; return true" onmouseout="window.status=''; return true"> +<IMG BORDER="0" SRC="/images/nav/p3.gif" WIDTH="157" HEIGHT="19" ALT="Y2K Central"></A><BR> +<A HREF="show.pl?target=security/sec" onmouseover="window.status='Security Information'; return true" onmouseout="window.status=''; return true"> +<IMG BORDER="0" SRC="/images/nav/p2.gif" WIDTH="157" HEIGHT="19" ALT="Security Information"></A><BR> +<br><table cellpadding="0" cellspacing="0" border="0" width="157"> +<tr><td width="8"> </td><td width="149"> +<table cellpadding="0" cellspacing="0" border="0"> +<BR><tr><td><BR><img src="/images/line.gif" alt="------" width="140" height="11" border="0"><br> + <A HREF="mark.pl" + onmouseover="window.status='Marked Docs.';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">Marked Docs.</FONT></A><BR> + <A HREF="notify.pl" + onmouseover="window.status='Notifications';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">Notifications</FONT></A><BR> + <A HREF="/plain-cgi/show.pl?target=home_con" + onmouseover="window.status='Low Graphics';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">Low Graphics</FONT></A><BR> + <A HREF="show.pl?target=link" + onmouseover="window.status='SunSolve Servers';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">SunSolve Servers</FONT></A><BR> + <A HREF="show.pl?target=about_sunsolve" + onmouseover="window.status='About SunSolve';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">About SunSolve</FONT></A><BR> + <A HREF="feedback.pl" + onmouseover="window.status='Contact Us';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">Contact Us</FONT></A><BR> + <A HREF="show.pl?target=help/sitemap" + onmouseover="window.status='Site Map';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">Site Map</FONT></A><BR> + <A HREF="show.pl?target=article/article" + onmouseover="window.status='Articles';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">Articles</FONT></A><BR> + <A HREF="show.pl?target=home_con" + onmouseover="window.status='Home';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">Home</FONT></A><BR> + <A HREF="show.pl?target=help/faq" + onmouseover="window.status='Help';return true" + onmouseout="window.status='';return true"> + <font class="locallink" color="#dddddd">Help</FONT></A><BR> +<br></td></tr></table></td></tr></table> +<!-- End of Nav area --> + + </FORM> + <br><br><!-- some spacers --> + </TD> + </TR> + </TABLE> + </TD> + <TD VALIGN="TOP" WIDTH="466"> + + + <!--startindex--> + <!-- ============ --> + <!-- MAIN CONTENT --> + <!-- ============ --> + + + +<table width=100% cellpadding=16 cellspacing=0 border=0> + <tr> +<td width=100% valign=top> +<CENTER><FONT FACE="Geneva, Helvetica, Arial, SunSans-Regular" SIZE="2"> +[ <a href="retrieve.pl?type=0&doc=srdb%2F19195&display=plain">Printer Friendly Page</a> ] +[ <b>Was this document useful? <a href="retrieve.pl?type=0&doc=srdb/19195&vote=yes">Yes</a> or <a href="retrieve.pl?type=0&doc=srdb/19195&vote=no">No</a></b> ]<br>[ <a href="notify.pl?action=add&doc=srdb%2F19195&type=synopsis">Notify if Document Changes</a> ] +[ <a href="mark.pl?action=add&doc=srdb%2F19195&type=0">Mark Document for Download</a> ]<br>[ <a href="notify.pl">View/Edit Notifications</a> ] +[ <a href="mark.pl">View/Edit Marked Documents</a> ]<br></FONT></CENTER><br> + <SCRIPT Language="JavaScript"> + <!-- Hide javascript from older browsers + function jump() + { + var ctl = document.docform.jumplist; + location.href = ctl.options[ctl.selectedIndex].value; + } + // End hiding contents --> + </SCRIPT> +<a name="top"> +<form name="docform"><div align=center><font size=2> Jump to <select name="jumplist" size=1 onchange="jump();"></font><option value="#Hardware">Hardware</option> +<option value="#Product">Product</option> +<option value="#Product-Area">Product Area</option> +<option value="#Synopsis">Synopsis</option> +<option value="#Problem-Description">Problem Description</option> +<option value="#Document-Content">Document Content</option> +<option value="#Problem-Solution">Problem Solution</option> +<option value="#SRDB-ID">SRDB ID</option> +<option value="#OS">OS</option> +</select></div></form> +<table width=100% cellpadding=2 cellspacing=0 border=0> +<tr bgcolor=#666699><td><font size=2 color=#ffffff><b>SRDB ID</b></font></td> +<td bgcolor=#ffffff><font size=2> </font></td> +<td><font size=2 color=#ffffff><b>Synopsis</b></font></td> +<td bgcolor=#ffffff><font size=2> </font></td> +<td><font size=2 color=#ffffff><b>Date</b></font></td> +</tr> +<tr bgcolor=#CCCCE7><td><font size=2><b>19195</b></font></td> +<td bgcolor=#ffffff><font size=2> </font></td> +<td><font size=2><b>Upgraded to 2.6, using xntpd, but the system clock is drifting. Worked fine</b></font></td> +<td bgcolor=#ffffff><font size=2> </font></td> +<td><font size=2><b>4 Sep 1999</b></font></td> +</tr> +</table><br clear> +<table width=100% cellpadding=2 cellspacing=0 border=0><tr bgcolor=#999999> +<td><font size=2 color=#ffffff><b><a name=Problem-Description>Problem Description</a></b></font></td> +<td align=right><b><a href="#top"><font size=2 color=#ffffff>Top</font></a></b></td></tr></table> +<pre>Ever since upgrading to Solaris 2.6, the system clock has been drifting and +there are messages like 'synchronisation lost', 'Previous time adjustment +didn''t complete' and 'time reset (step)' a lot in the /var/adm/messages +file. The system either was previously working fine with the freeware +xntpd or the configuration was copied from another system that was +using the freeware version. +-- 23-Apr-99 08:22 US/Eastern --</pre><table width=100% cellpadding=2 cellspacing=0 border=0><tr bgcolor=#999999> +<td><font size=2 color=#ffffff><b><a name=Problem-Solution>Problem Solution</a></b></font></td> +<td align=right><b><a href="#top"><font size=2 color=#ffffff>Top</font></a></b></td></tr></table> +<pre>The common lore for setting up xntpd on Solaris using +the freeware version included the warning to set the +kernel variable <font color=red>dosynctodr</font> to 0 in the /etc/system +file thus: set <font color=red>dosynctodr</font>=0 + +When using NTP on Solaris 2.6 or later, the kernel +variable MUST be left at the default value of 1. Prior +to 2.6 this variable controlled whether or not to rein +in the softclock using the hardware clock, with the result +that NTP and the hardware clock would fight for control of +the soft clock; thus before 2.6 you had to set <font color=red>dosynctodr</font> +to 0. At 2.6, every system call that adjusts the softclock +also sets the hard clock, thus while NTP controls the soft +clock, the hard clock is also controlled. Setting +<font color=red>dosynctodr</font> to 0 reverts the behavior back to the pre 2.6 +defaulkt behavior, having exactly the opposite effect +as that intended. + +Do not set <font color=red>dosynctodr</font> to 0.</pre><table width=100% cellpadding=2 cellspacing=0 border=0> +<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=Product-Area>Product Area</a></b></font></td> +<td bgcolor=#cccccc valign=top width=75%><font size=2>Bundled Network</font></td></tr> +<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=Product>Product</a></b></font></td> +<td bgcolor=#cccccc valign=top width=75%><font size=2>NTP</font></td></tr> +<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=OS>OS</a></b></font></td> +<td bgcolor=#cccccc valign=top width=75%><font size=2>Solaris 2.6</font></td></tr> +<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=Hardware>Hardware</a></b></font></td> +<td bgcolor=#cccccc valign=top width=75%><font size=2>Ultra 2</font></td></tr> +<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=Document-Content>Document Content</a></b></font></td> +<td bgcolor=#cccccc valign=top width=75%><font size=2>with freeware xntpd.</font></td></tr> +</table><br clear> +<font size=2><a href="#top">Top</a></font><br><br> +</td></tr></table> + + <!-- =================== --> + <!-- END OF MAIN CONTENT --> + <!-- =================== --> + <!--stopindex--> + + <!-- DON'T CHANGE INFORMATION OTHER THAN titlebar BELOW THIS LINE --> + + <!-- Altered Table Structure from Template to format properly with new design --> + </TD> + </TR> + <TR> + <TD> </TD> + <TD VALIGN="top"> + <center> + <IMG SRC="/images/cg_grey_line.gif" ALT="" WIDTH="466" HEIGHT="2" BORDER="0"><BR> + <IMG SRC="/images/cg_clear.gif" ALT="" WIDTH="1" HEIGHT="2" BORDER="0" HSPACE="0" VSPACE="4"> + </center> + <CENTER> + <FONT FACE="Geneva, Helvetica, Arial, SunSans-Regular" SIZE="2"> + [ <A HREF="edit-user-form.pl?viewmode=contractuser">Edit Account</A> ] + [ <A HREF="show.pl?target=patches/patch-access">Patches</A> ] + [ <A HREF="suncourier.pl">Submit a Service Order</A> ]<br> + [ <A HREF="show.pl?target=resources/tools">Diagnostic Tools</A> ] + [ <A HREF="show.pl?target=help/collections">Support Docs.</A> ] + [ <A HREF="show.pl?target=resources/y2k">Y2K Central</A> ] + [ <A HREF="show.pl?target=security/sec">Security Information</A> ] <br> + [ <A HREF="show.pl?target=link">SunSolve Servers </A> ] + [ <A HREF="show.pl?target=about_sunsolve">About SunSolve</A> ] + [ <A HREF="feedback.pl">Contact Us</A> ] + [ <A HREF="show.pl?target=help/sitemap">Site Map</A> ] + [ <A HREF="show.pl?target=article/article">Articles</A> ] + [ <A HREF="show.pl?target=home_con">Home</A> ] + [ <A HREF="show.pl?target=help/faq">Help</A> ] + </FONT> + </CENTER> + +<!-- MAPS --> +<MAP NAME="lefttop"> +<AREA SHAPE="rect" HREF="http://www.sun.com/MySun/" ALT="My Sun" COORDS="89,0 149,32"> +<AREA SHAPE="rect" HREF="show.pl?target=home_con" ALT="Home" COORDS="0,0 42,32"> +<AREA SHAPE="rect" HREF="http://www.sun.com/sales/" ALT="Buy" COORDS="54,0 78,32"> +</MAP> + + +<MAP NAME="topnav"> +<AREA SHAPE="rect" HREF="http://www.sun.com/java/" ALT="Java Technologies" COORDS="4,0,67,32"> +<AREA SHAPE="rect" HREF="http://www.sun.com/products-n-solutions/" ALT="Products and Solutions" COORDS="74,0,141,32"> +<AREA SHAPE="rect" HREF="http://www.sun.com/service/" ALT="Support, Education, and Consulting" COORDS="148,0,249,32"> +<AREA SHAPE="rect" HREF="http://www.sun.com/tech/" ALT="Technology and Research" COORDS="261,0,324,32"> +<AREA SHAPE="rect" HREF="http://www.sun.com/developers/developers.html" ALT="For Developers" COORDS="334,0,396,32"> +<AREA SHAPE="rect" HREF="http://www.sun.com/corporateoverview/" ALT="Corporate Information" COORDS="406,0,482,32"> +</MAP> + +<!-- INSERT titlebar HREFS BELOW --> +<MAP NAME="titlebar"> +<!-- LINK TO SEC HOME Removed because no longer needed on this template --> +<AREA SHAPE="rect" HREF="/visual/home/" ALT="SunSolve Online(tm)" COORDS="0,21,215,51"> <!-- LINK TO CURRENT PILL HOME --> +</MAP> + + +<!-- begin copyright notice --> + +<BR> +<CENTER> +<FONT FACE="Geneva, Helvetica, Arial, SunSans-Regular" COLOR="#999999" SIZE="2"> +<br> +Copyright 1994-1999 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303 USA. +<br> +All rights reserved. +<a href="http://www.sun.com/share/text/SMICopyright.html">Legal Terms</a>. +<a href="http://www.sun.com/privacy/">Privacy Policy</a>. +</font> +</CENTER> + +<!-- end copyright notice --> + + </TD> + </TR> +</TABLE> + +</BODY> +</HTML> + diff --git a/html/hints/solaris.html b/html/hints/solaris.html new file mode 100644 index 0000000..4b83862 --- /dev/null +++ b/html/hints/solaris.html @@ -0,0 +1,236 @@ +<HTML> +<HEAD> +<TITLE>Solaris hints and kinks</title><link href="scripts/style.css" type="text/css" rel="stylesheet"> + +</HEAD> +<BODY> +Information on compiling and executing ntpd under Solaris. +<BR> +<p>Last update: + <!-- #BeginDate format:En2m -->27-Jan-2014 05:31<!-- #EndDate --> + UTC, +John Hawkinson, +<! -- This is deliberately not a mailto -- > <jhawk@MIT.EDU> +</p> +<P> +If you're not running Solaris 2.5.1 or later, it is likely +that you will have problems; upgrading would be a really good plan. +<P> +<H3>All Solaris versions</H3> +<P> + We have a report that says starting with Solaris 2.6 we should leave + <I>dosynctodr</I> alone. + <A HREF="solaris-dosynctodr.html">Here is the report</A>. +<P> +Proper operation of ntp under Solaris may require setting the kernel +variable <I>dosynctodr</I> to zero (meaning "do not synchronize the clock +to the hardware time-of-day clock"). This can be done with the +tickadj utility: +<BLOCKQUOTE><TT> +tickadj -s +</TT></BLOCKQUOTE> +If you prefer, it can also be done with the native Solaris kernel debugger: +<BLOCKQUOTE><TT> +echo dosynctodr/W0 | adb -k -w /dev/ksyms /dev/mem +</BLOCKQUOTE></TT> +<P> +Or, it can also be set by adding a line to /etc/system: +<BLOCKQUOTE><TT> +set dosynctodr = 0 +</BLOCKQUOTE></TT> +<P> +Instead of the <I>tick</I> kernel variable, which many operating +systems use to control microseconds added to the system time every +clock tick (c.f. <A HREF="#frequency_tolerance">Dealing +with Frequency Tolerance Violations</A>), Solaris has the variables +<I>nsec_per_tick</I> and <I>usec_per_tick</I>. +<P> +<I>nsec_per_tick</I> and <I>usec_per_tick</I> control the number of +nanoseconds and microseconds, respectively, added to the system clock +each clock interrupt. Enterprising souls may set these based on +information collected by ntpd in the <CODE>/etc/ntp.drift</CODE> file +to correct for individual hardware variations. +<P> +On UltraSPARC systems, <I>nsec_per_tick</I> and <I>usec_per_tick</I> +are ignored in favor of the <I>cpu_tick_freq</I> variable, which +should be automatically be determined by the PROM in an accurate +fashion. +<P> +In general, the same ntp binaries should not be used across multiple +operating system releases. There is enough variation in the core operating +system support for timekeeping that a rebuild of ntpd for the idiosyncracies +of your specific operating system version is advisable. +<P> +It is recommended that ntp be started via a script like <A +HREF="solaris.xtra.S99ntpd">this one</A>, installed in +<CODE>/etc/init.d/ntpd</CODE> with a symbol link from +<CODE>/etc/rc2.d/S99ntpd</CODE>. + +<a id="frequency_tolerance" /> +<h4>Dealing with Frequency Tolerance Violations (<tt>tickadj</tt> and +Friends)</h4> + The NTP Version 3 specification RFC-1305 calls for a maximum + oscillator frequency tolerance of +-100 parts-per-million (PPM), which is +representative of those components suitable for use in relatively +inexpensive workstation platforms. For those platforms meeting this +tolerance, NTP will automatically compensate for the frequency errors of the +individual oscillator and no further adjustments are required, either to the +configuration file or to various kernel variables. For the NTP Version 4 +release, this tolerance has been increased to +-500 PPM. <p>However, in the +case of certain notorious platforms, in particular Sun 4.1.1 systems, the +performance can be improved by adjusting the values of certain kernel +variables; in particular, <tt>tick</tt> and <tt>tickadj</tt>. The variable +<tt>tick</tt> is the increment in microseconds added to the system time on +each interval- timer interrupt, while the variable <tt>tickadj</tt> is used +by the time adjustment code as a slew rate, in microseconds per tick. When +the time is being adjusted via a call to the system routine +<tt>adjtime()</tt>, the kernel increases or reduces tick by <tt>tickadj</tt> +microseconds per tick until the specified adjustment has been +completed. Unfortunately, in most Unix implementations the tick increment +must be either zero or plus/minus exactly <tt>tickadj</tt> microseconds, +meaning that adjustments are truncated to be an integral multiple of +<tt>tickadj</tt> (this latter behaviour is a misfeature, and is the only +reason the <tt>tickadj</tt> code needs to concern itself with the internal +implementation of <tt>tickadj</tt> at all). In addition, the stock Unix +implementation considers it an error to request another adjustment before a +prior one has completed.</p> <p>Thus, to make very sure it avoids problems +related to the roundoff, the <tt>tickadj</tt> program can be used to adjust +the values of <tt>tick</tt> and <tt>tickadj</tt>. This ensures that all +adjustments given to <tt>adjtime()</tt> are an even multiple of +<tt>tickadj</tt> microseconds and computes the largest adjustment that can +be completed in the adjustment interval (using both the value of +<tt>tick</tt> and the value of <tt>tickadj</tt>) so it can avoid exceeding +this limit. It is important to note that not all systems will allow +inspection or modification of kernel variables other than at system build +time. It is also important to know that, with the current NTP tolerances, it +is rarely necessary to make these changes, but in many cases they will +substantially improve the general accuracy of the time service.</p> +<p>Unfortunately, the value of <tt>tickadj</tt> set by default is almost +always too large for <tt>ntpd</tt>. NTP operates by continuously making +small adjustments to the clock, usually at one-second intervals. If +<tt>tickaj</tt> is set too large, the adjustments will disappear in the +roundoff; while, if <tt>tickadj</tt> is too small, NTP will have difficulty +if it needs to make an occasional large adjustment. While the daemon itself +will read the kernel's values of these variables, it will not change the +values, even if they are unsuitable. You must do this yourself before the +daemon is started using the <tt>tickadj</tt> program included in the +<tt>./util</tt> directory of the distribution. Note that the latter program +will also compute an optimal value of <tt>tickadj</tt> for NTP use based on +the kernel's value of <tt>tick</tt>.</p> <p>The <tt>tickadj</tt> program can +reset several other kernel variables if asked. It can change the value of +<tt>tick</tt> if asked. This is handy to compensate for kernel bugs which +cause the clock to run with a very large frequency error, as with SunOS +4.1.1 systems. It can also be used to set the value of the kernel +<tt>dosynctodr</tt> variable to zero. This variable controls whether to +synchronize the system clock to the time-of-day clock, something you really +don't want to be happen when <tt>ntpd</tt> is trying to keep it under +control. In some systems, such as recent Sun Solaris kernels, the +<tt>dosynctodr</tt > variable is the only one that can be changed by the +<tt>tickadj</tt> program. In this and other modern kernels, it is not +necessary to change the other variables in any case.</p> + +<p>We have a report that says starting with Solaris 2.6 we should leave +<i>dosynctodr</i> alone.</p> <p>In order to maintain reasonable correctness +bounds, as well as reasonably good accuracy with acceptable polling +intervals, <tt>ntpd</tt> will complain if the frequency error is greater +than 500 PPM. For machines with a value of <tt>tick</tt> in the 10-ms range, +a change of one in the value of <tt>tick</tt> will change the frequency by +about 100 PPM. In order to determine the value of <tt>tick</tt> for a +particular CPU, disconnect the machine from all source s of time +(<tt>dosynctodr</tt> = 0) and record its actual time compared to an outside +source (eyeball-and-wristwatch will do) over a day or more. Multiply the +time change over the day by 0.116 and add or subtract the result to tick, +depending on whether the CPU is fast or slow. An example call to +<tt>tickadj</tt> useful on SunOS 4.1.1 is:</p> + <pre> + <tt>tickadj</tt> -t 9999 -a 5 -s +</pre> +which sets tick 100 PPM fast, <tt>tickadj</tt> to 5 microseconds and turns +off the clock/calendar chip fiddle. This line can be added to the <tt +>rc.local</tt> configuration file to automatically set the kernel variables +at boot time. <p>All this stuff about diddling kernel variables so the NTP +daemon will work is really silly. If vendors would ship machines with clocks +that kept reasonable time and would make their <tt>adjtime()</tt> system +call apply the slew it is given exactly, independent of the value of +<tt>tickadj</tt>, all this could go away. This is in fact the case on many +current Unix systems.</p> + +<H3>Solaris 2.6</H3> +<P> +Solaris 2.6 adds support for kernel PLL timekeeping, but breaks this +support in such a fashion that using it worse than not. This is <A +HREF="solaris.xtra.4095849"> SUN Bug ID 4095849</A>, and it is not yet +fixed as of June 1998. +<P> +<H3>Solaris 2.5 and 2.5.1</H3> +<P> +On UltraSPARC systems, calculation of <I>cpu_tick_freq</I> is broken +such that values that are off by significant amounts may be used +instead. This unfortunately means that ntpd may have severe problems +keeping synchronization. This is <A HREF="solaris.xtra.4023118"> SUN Bug ID +4023118</A>. Bryan Cantrill <! -- <bmc@eng.sun.com> --> of Sun +posted <A HREF="solaris.xtra.patchfreq">patchfreq</A>, a workaround script, +to comp.protocols.time.ntp in March of 1997. +<P> +<HR> +<H2>OLD DATA</H2> +<STRONG>I can't vouch for the accuracy the information below this +rule. It may be significantly dated or incorrect.</STRONG> +<P> +<P> +<H3>Solaris 2.2</H3> +<P> +Solaris 2.2 and later contain completely re-written clock code to +provide high resolution microsecond timers. A benefit of the +re-written clock code is that adjtime does not round off its +adjustments, so ntp does not have to compensate for this +rounding. Under Solaris 2.2 and later, ntp #define's +<CODE>ADJTIME_IS_ACCURATE</CODE>, and does not look for the <I>tickadj</I> +kernel variable. +<P> +<H3>Solaris 2.1</H3> +(This originally written by William L. Jones <jones@chpc.utexas.edu>) +<P> +Solaris 2.1 contains fairly traditional clock code, with <I>tick</I> +and <I>tickadj</I>. +<P> +Since settimeofday under Solaris 2.1 only sets the seconds part of timeval +care must be used in starting xntpd. I suggest the following start +up script: +<BLOCKQUOTE><TT> +tickadj -s -a 1000 +<BR>ntpdate -v server1 server2 +<BR>sleep 20 +<BR>ntpdate -v server1 server2 +<BR>sleep 20 +<BR>tickadj -a 200 +<BR>xntpd +</TT></BLOCKQUOTE> + +The first tickadj turns of the time of day clock and sets the tick +adjust value to 1 millisecond. This will insure that an adjtime value +of at most 2 seconds will complete in 20 seconds. +<P> +The first ntpdate will set the time to within two seconds +using settimeofday or it will adjust time using adjtime. +<P> +The first sleep insures the adjtime has completed for the first ntpdate. +<P> +The second ntpdate will use adjtime to set the time of day since the +clock should be within 2 seconds of the correct time. +<P> +The second tickadj set the tick adjust system value to 5 microseconds. +<P> +The second sleeps insure that adjtime will complete before starting +the next xntpd. +<P> +I tried running with a tickadj of 5 microseconds with out much success. +200 microseconds seems to work well. +<P> +<HR> +Prior versions of this file had major text contributed by: +<MENU> +<LI>Denny Gentry <denny@eng.sun.com> +</MENU> +<BODY> +</HTML> diff --git a/html/hints/solaris.xtra.4023118 b/html/hints/solaris.xtra.4023118 new file mode 100644 index 0000000..84c5d15 --- /dev/null +++ b/html/hints/solaris.xtra.4023118 @@ -0,0 +1,36 @@ + Bug Id: 4023118 + Category: kernel + Subcategory: other + State: integrated + Synopsis: sun4u doesn't keep accurate time + Description: + +[ bmc, 12/20/96 ] + +The clock on a sun4u drifts unacceptably. On a typical 143 mHz Ultra, +the clock took 1.0001350 seconds to count 1 second. While this may seem +trivial, it adds up quickly. In this case, the TOD chip will have to +pull the clock forward by 2 seconds every 4 hours and 7 minutes. +This drift rate is so high, that the clock is close to being too broken +for NTP to guarantee correctness (in order for NTP's mechanism to work, +it must be assured that the local clock drifts no more than 20 ms in 64 +seconds; this particular 143 mHz Ultra will drift by nearly 9 ms in that +period). This problem has been reproduced on virtually all sun4u +classes. + +The fundamental problem lies in the kernel's perception of ticks per +second. The PROM is responsible for determining this figure exactly, +and the kernel extracts it into the variable cpu_tick_freq. On sun4u's, +this number is disconcertingly round: 143000000, 167000000, 248000000, +etc. Indeed, a simple experiment revealed that these numbers were +quite far from the actual ticks per second. Typical was the 143 mHz +Ultra which was discovered to tick around 142,980,806 (+/- 10) times +per second. + + Work around: + + Integrated in releases: s297_27 + Duplicate of: + Patch id: + See also: + Summary: diff --git a/html/hints/solaris.xtra.4095849 b/html/hints/solaris.xtra.4095849 new file mode 100644 index 0000000..8d3ce80 --- /dev/null +++ b/html/hints/solaris.xtra.4095849 @@ -0,0 +1,74 @@ + Bug Id: 4095849 + Category: kernel + Subcategory: syscall + State: evaluated + Synopsis: time_constant value >6 with PLL in use leads to integer divide + zero trap panic + Description: +If the time_constant parameter is 7 or higher, and the phase-lock looping model +is in use, the system will take a "integer divide zero trap" panic in +the clock routine as soon as the time_offset becomes non-zero. + +time_constant defaults to 0. The only place it is set is in the ntp_adjtime +system call, from the 'constant' element of the timex structure argument. + + Work around: +Never set the constant element of the timex structure passed to ntp_adjtime to +a value larger than 6. + +satish.mynam@Eng 1998-04-30 +1. Use Sun's version of NTP software instead of PD version. This problem +is not seen with Sun's NTP version (which is mostly eqivalent to PD NTP 3.4 +plus some Sun's local functionality futures). + +2. Workaround for the public domain NTP version ONLY: + ===================================================== +The workaround for public domain NTP version is to disable the +KERNEL_PLL from the NTP code. This way ntp_Adjtime() system call is +totally bypassed without sacrificing any of the functionality of the +NTP. The only hit you might see is the way kernel precision timminig +is done without the PLL algorithm in the kernel. + + The easiest way to disable ntp_adjtime option is(without changing + any makefiles or other config files) to disable the KERNEL_PLL + value in the ./config.h file. + +After doing a ./configure for probing for all the necessary tools(compilers, +os version, libraries), please comment out KERNEL_PLL macro in +the ./config.h file. This will disable the KERNEL_PLL part of the source +code and the newly obtained xntpd is just similar to the old one but it +does not use ntp_adjtime() system call. This prevents it from panic'ng +the kernel. + +/*#define KERNEL_PLL 1*/ + +I complied a new xntpd binary this way and it does nothave any ntp_adjtime() +related stuff. + +Default: +======= +/net/divya/export/home/mynam/public_domain/ntp/xntp3-5.92/xntpd>strings +xntpd | +grep ntp_adjtime +354:adj_frequency: ntp_adjtime failed: %m +357:loop_config: ntp_adjtime() failed: %m +435:get_kernel_info: ntp_adjtime() failed: %m + +With KERNEL_PLL disabled in config.h file +-======================= + +/net/divya/export/home/mynam/public_domain/ntp/xntp3-5.92/xntpd>strings +xntpd.nopll | grep ntp_adjtime + + Integrated in releases: + Duplicate of: + Patch id: + See also: 4133517 + Summary: +If the time_constant parameter is 7 or higher, and the phase-lock looping model +is in use, the system will take a "integer divide zero trap" panic in +the clock routine as soon as the time_offset becomes non-zero. + +time_constant defaults to 0. The only place it is set is in the ntp_adjtime +system call, from the 'constant' element of the timex structure argument. +---------------------------------------------------------------------------- diff --git a/html/hints/solaris.xtra.S99ntpd b/html/hints/solaris.xtra.S99ntpd new file mode 100644 index 0000000..d8058fd --- /dev/null +++ b/html/hints/solaris.xtra.S99ntpd @@ -0,0 +1,21 @@ +#!/bin/sh +if [ $1 = "start" ]; then + if [ -x /usr/local/bin/xntpd ]; then + echo "Starting NTP daemon, takes about 1 minute... " + # dosynctodr may need to be left alone as of with Solaris 2.6 + # The following line is unnecessary if you turn off + # dosynctodr in /etc/system. + /usr/local/bin/tickadj -s + /usr/local/bin/ntpdate -v server1 server2 + sleep 5 + /usr/local/bin/xntpd + fi +else + if [ $1 = "stop" ]; then + pid=`/usr/bin/ps -e | /usr/bin/grep xntpd | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` + if [ "${pid}" != "" ]; then + echo "Stopping Network Time Protocol daemon " + /usr/bin/kill ${pid} + fi + fi +fi diff --git a/html/hints/solaris.xtra.patchfreq b/html/hints/solaris.xtra.patchfreq new file mode 100644 index 0000000..9600881 --- /dev/null +++ b/html/hints/solaris.xtra.patchfreq @@ -0,0 +1,85 @@ +#!/bin/ksh + +# +# File: patchfreq +# Author: Bryan Cantrill (bmc@eng.sun.com), Solaris Performance +# Modified: Sat Apr 26 04:00:59 PDT 1997 +# +# This is a little script to patch a 5.5 or 5.5.1 kernel to get around +# the cpu_tick_freq inaccuracy. Before running this script, one must +# know the true frequency of one's CPU; this can be derived by NTP, +# or by observing the clock relative to the time-of-day chip over a +# long period of time (the TOD will pull system time when it drifts +# by more than two seconds). +# +# Patching a kernel can render a machine unbootable; do not run this +# script unless you are prepared to accept that possibility. It +# is advisable to have a backout path (e.g. net booting, an alternate +# boot disk, an installation CD) should your machine fail to boot. +# +# This is not a product of Sun Microsystems, and is provided "as is", +# without warranty of any kind expressed or implied including, but not +# limited to, the suitability of this script for any purpose. +# + +if [ $# -eq 0 ]; then + echo "Usage: $0 cpu_tick_freq [ alternate_kernel ]" + exit 1 +fi + +cpu_tick_freq=$1 +kernel=/platform/sun4u/kernel/unix + +if [ $# -eq 2 ]; then + kernel=$2 +fi + +if [ ! -w $kernel ]; then + echo "$0: Cannot open $kernel for writing." + exit 1 +fi + +arch=`echo utsname+404?s | adb $kernel | cut -d: -f2` + +if [ ! $arch = "sun4u" ]; then + echo "Patch only applies to sun4u" + exit 1 +fi + +rel=`echo utsname+202?s | adb $kernel | cut -d: -f2` + +if [ ! $rel = "5.5" ] && [ ! $rel = "5.5.1" ]; then + echo "Patch only applies to 5.5 or 5.5.1..." + exit 1 +fi + +nop="1000000" # nop +store_mask="ffffe000" # mask out low 13 bits +store="da256000" # st %o5, [%l5 + offset] + +instr=`echo setcpudelay+34?X | adb $kernel | cut -d: -f 2 | nawk '{ print $1 }'` + +if [ $instr = $nop ]; then + echo "Instruction already patched..." +else + let masked="(16#$store_mask & 16#$instr) - 16#$store" + if [ $masked -ne 0 ]; then + echo "Couldn't find instruction to patch; aborting." + exit 1 + fi + + if ! echo setcpudelay+34?W $nop | adb -w $kernel 1> /dev/null + then + echo "adb returned an unexpected error; aborting." + fi +fi + +echo "Patching cpu_tick_freq to $cpu_tick_freq..." + +if ! echo cpu_tick_freq?W 0t$cpu_tick_freq | adb -w $kernel 1> /dev/null; then + echo "adb returned an unexpected error; aborting." + exit 1 +fi + +echo "$kernel successfully patched." +exit 0 diff --git a/html/hints/sun4 b/html/hints/sun4 new file mode 100644 index 0000000..424fa18 --- /dev/null +++ b/html/hints/sun4 @@ -0,0 +1,15 @@ +Notes on CPU clock oscillator tolerance with SunOS 4.1.1 and 4.1.3 + +A bug in SunOS 4.1.1 results in the kernel time losing 1 microsecond +per tick of the system clock. The bug was fixed (bugid 1094383) for +SunOS 4.1.1 and corrected in SunOS 4.1.3. The easiest way to fix this +is to replace the 4.1.1 binary clock.o with the corresponding 4.1.3 +binary. Without this change it is necessary to use the tickadj program +included in this distribution with the -t 9999 option. + +The tickadj option will work in all cases except when the kernel has +been modified to correct the CPU clock oscillator frequency using a +1-pps signal from a precision source. The bugfix must be installed for +this wrinkle to work properly. + +Dave Mills (mills@udel.edu) diff --git a/html/hints/svr4-dell b/html/hints/svr4-dell new file mode 100644 index 0000000..2c92f8a --- /dev/null +++ b/html/hints/svr4-dell @@ -0,0 +1,8 @@ +Notes on the DELL SVR4. + +You should use -DSETTIMEOFDAY_BROKEN. + +Philip.Gladstone@mail.citicorp.com + +(XXX But there is no checking for SETTIMEOFDAY_BROKEN in the code) + diff --git a/html/hints/svr4_package b/html/hints/svr4_package new file mode 100644 index 0000000..b9f5ca3 --- /dev/null +++ b/html/hints/svr4_package @@ -0,0 +1,33 @@ +Date: Wed, 12 Apr 1995 12:42:03 +0100 +Message-ID: <513.797686923@concurrent.co.uk> +From: Andy Chittenden <asc@concurrent.co.uk> + +Dave + +Here is a uuencoded, compressed tar file. The only file I've +changed is Makefile - I've included the full file rather than diffs. +There are some new files as well: + + xntp shell script that starts up ntp during boot up + (the packaging stuff creates links to it so it comes + up at run level 2). As with all svr4 start/stop + scripts, it takes one parameter which is either + start or stop. It assumes that ntp.conf is in + /etc/inet/ntp.conf (where it should be on svr4 + machines). + prototype describes the file contents of the package. + You might like to review its contents to + see whether you want to include any other + files or remove some. NB I've made the man + pages go into 1m as they should on svr4. + preinstall runs before installation takes place. It + ensures that ntp is down if it is up before + installing a replacement package + postinstall starts up ntp after package installation. + preremove brings down ntp before removing the package. + +You create a package using "make package". This creates a file +called xntp.pkg. To install this package, you use +"pkgadd -d `pwd`/xntp.pkg xntp". This will start up ntp if +/etc/inet/ntp.conf exists. If you don't want the package anymore, use +"pkgrm xntp". I have tested this on Solaris 2.4. diff --git a/html/hints/todo b/html/hints/todo new file mode 100644 index 0000000..e0e5ffa --- /dev/null +++ b/html/hints/todo @@ -0,0 +1,4 @@ +Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>: + Any change in a source file in the lib directory causes all files to + be recompiled (because the objects are removed). Add a better rule for + make to update the library. Maybe just remove "-rm -f $?". diff --git a/html/hints/vxworks.html b/html/hints/vxworks.html new file mode 100644 index 0000000..eac9312 --- /dev/null +++ b/html/hints/vxworks.html @@ -0,0 +1,88 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> + +<html> + + <head> + <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> + <meta name="generator" content="HTML Tidy, see www.w3.org"> + <title>vxWorks Port of NTP</title> + <link href="../scripts/style.css" type="text/css" rel="stylesheet"> + </head> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> + + <body link="#00008B" vlink="#8B0000"> + <h4>VxWorks port of NTP</h4> +<p>Last update: + <!-- #BeginDate format:En2m -->21-Oct-2010 23:44<!-- #EndDate --> + UTC</p> + <p>Creating a port for vxWorks posed some problems. This port may help as a starting point for similar ports to real-time OS's and other embeddable kernels, particularly where <tt>main()</tt> is not allowed, and where the configure scripts need to be altered.</p> + <h4>Configuration issues</h4> + <p>I decided to do as little invasive surgery as possible on the NTP code, so I brought the vxWorks header tree in line with the standard Unix tree. The following changes were needed, as a side effect these changes will allow for easy porting of other autoconfigure enabled code.</p> + <p>Where I have 386 you will need to put in your target type. The vxWorks tree entry point is <tt>/usr/wind</tt>. If these are the same for your system, you should be able to cut and paste the changes.</p> + <p><blink>WARNING: Check you are not overwriting files, before entering the following: there should be no conflict, but check first...</blink></p> + <pre> + export CC="cc386 -nostdlib -m486 -DCPU=I80486 -I/usr/wind/target/h" + export RANLIB=ranlib386 + export AR=ar386 + export VX_KERNEL=/usr/wind/target/config/ims_std_bsp/vxWorks<br> + + cd /usr/wind/target/sys + ln -s ../signal.h + ln -s ../time.h + ln -s socket.h sockio.h + ln -s ../selectLib.h select.h + ln -s ../timers.h + touch file.h param.h resource.h utsname.h var.h ../netdb.h ../a.out.h ../termios.h + echo " ******ADD #include \"sys/times.h\" to sys/time.h " + </pre> + The configure script must be changed in the following way to get the linking tests to work, once in the correct directory issue the following commands: + + <pre> sed -e 's%main.*()%vxmain()%' configure > configure.vxnew + mv configure.vxnew configure + chmod 755 configure + </pre> + <p></p>The new version 4 of NTP requires some maths functions so it links in the maths library (-lm) in the <tt>./ntpd/Makefile.am</tt> file change the line <tt>ntpd_LDADD = $(LDADD) -lm</tt> by removing the "-lm".</p> + <p>>You are now ready to compile + <p>The ./configure.in file needed to be altered to allow for a host-target configuration to take place.</p> + <ul> + <li>The define SYS_VXWORKS was added to the compilation flags. + <li>Little endianess is set if the target is of type iX86. + <li>The size of char, integer, long values are all set. If Wind River ever changes these values they will need to be updated. + <li>clock_settime() is defined to be used for setting the clock. + <li>The Linking flags have -r added to allow for relinking into the vxWorks kernel + </ul> + <p>Unfortunately I have had to make use of the <tt>./include/ntp_machine.h</tt> file to add in the checks that would have been checked at linking stage by <tt>autoconf</tt>, a better method should be devised.</p> + <ul> + <li>There is now a <tt>NO_MAIN_ALLOWED</tt> define that simulates command line args, this allows the use of the normal startup sysntax. + <li>POSIX timers have been added. + <li>Structures normally found in <tt>netdb.h</tt> have been added with, the corresponding code is in <tt>./libntp/machines.c</tt>. Where possible the defines for these have been kept non-vxWorks specific. + </ul> + <p>Unfortunately there are still quite a few <tt>SYS_VXWORKS</tt> type defines in the source, but I have eliminated as many as possible. You have the choice of using the <tt>usrtime.a</tt> library avaliable from the vxworks archives or forgoing <tt>adjtime()</tt> and using the <tt>clock_[get|set]time()</tt>. The <tt>./include/ntp_machine.h</tt> file clearly marks how to do this.</p> + <h4>Compilation issues</h4> + <p>You will need autoconf and automake ... available free from the gnu archives worldwide.</p> + <p>The variable <tt>arch</tt> is the target architecture (e.g. i486)</p> + <pre> + mkdir A.vxworks) + cd A.vxworks + ../configure --target=arch-wrs-vxworks + make + </pre> + <p>Options I normally use are the <tt>--disable-all-clocks --enable-LOCAL-CLOCK</tt> flags. The program should proceed to compile without problem. The daemon ntpd, ntpdate, ntptrace, ntpdc, ntpq programs and of course the libraries are all fully ported. The other utilities are not, but they should be easy to port.</p> + <h4>Running the software</h4> + <p>Load in the various files, call them in the normal vxWorks function type manner. Here are some examples. Refer to the man pages for further information.</p> + <pre> + ld < ntpdate/ntpdate + ld < ntpd/ntpd + ld < ntptrace/ntptrace + ld < ntpq/ntpq + ld < ntpdc/ntpdc + ntpdate ("-b", "192.168.0.245") + sp(ntpd, "-c", "/export/home/casey/ntp/ntp.conf") + ntpdc("-c", "monlist", "192.168.0.244") + ntpq("-c", "peers", "192.168.0.244") + ntptrace("192.168.0.244") + </pre> + <p>Casey Crellin, casey@csc.co.za</p> + </body> + +</html> diff --git a/html/hints/winnt.html b/html/hints/winnt.html new file mode 100644 index 0000000..7c41b86 --- /dev/null +++ b/html/hints/winnt.html @@ -0,0 +1,90 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> + +<html> + + <head> + <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> + <meta name="generator" content="HTML Tidy, see www.w3.org"> + <title>NTP on Windows NT</title> + <link href="../scripts/style.css" type="text/css" rel="stylesheet"> + </head> + <body> + <h3>NTP 4.x for Windows</h3> + + <h4>Introduction</h4> + <p>The NTP 4 distribution runs as service on Windows 2000 and later. It will NOT run on Windows 95, 98, ME, etc. Lately it has been run the most on Windows-7 and later. The binaries work on multi-processor systems. This port has not been tested on the Alpha platform. This release now uses OpenSSL for authentication. IPv6 is not implemented yet for Win32 platforms. A ready-to-run install distribution is available from Meinberg at <a href="http://www.meinberg.de/english/sw/ntp.htm">http://www.meinberg.de/english/sw/ntp.htm.</a></p> + <p>Users should note that the stock Windows client sends requests as mode-1 packets, which can have unintended consequences and create a security risk. The client should send requests as mode-3 (client) packets, which conform to the protocol specification. The issues and resolution are described in Microsoft KB 875424. A less desirable alternative that avoids changing registry keys is to use the <tt>--with-wintime</tt> option when building the executable.</p> + <h4>Authentication Keys</h4> + <p>With this release ntp-keygen is supported. See the <a href="../keygen.html"> ntp keygen documentation</a> for details on how to use ntp-keygen.</p> + <p><tt>ntpd</tt> can now use the generated keys in the same way as on Unix platforms. Please refer to the <a href="../authopt.html">Authentication Options</a> for details on how to use these.</p> + <p><B>NOTE:</B> ntpd and <tt>ntp-keygen</tt> both use OpenSSL which requires a random + character file called <tt>.rnd</tt> by default. Both of these programs will automatically generate this file if they are not found. The programs will look for an environmental variable called RANDFILE and use that for the name of the random character file if the variable exists. If it does not exist it will look for an environmental variable called HOME and use that directory to search for a file called <tt>.rnd</tt> in that directory. Finally, if neither RANDFILE nor HOME exists it will look in <tt>C:\</tt> for a .rnd file. In each case it will search for and create the file if the environmental variable exists or in the C:\ directory if it doesn't.</p> + <p>Note that ntpd normally runs as a service so that the only way that it will have either RANDFILE or HOME defined is if it is a System environmental variable or if the service is run under a specific account name and that account has one of those variables defined. Otherwise it will use the file <tt>c:\.rnd</tt>. This was done so that OpenSSL will work normally on Win32 systems. This obviates the need to ship the OpenSSL.exe file and explain how to generate the .rnd file. A future version may change this behavior.</p> + <p>Refer to <a href="#Compiling">Compiling Requirements</a> and Instructions for how to compile the program.</p> + <h4>Reference Clocks</h4> + <p>Reference clock support under Windows NT is tricky because the IO functions are so much different. Some of the clock types have been built into the ntpd executable and should work but have not been tested by the ntp project. If you have a clock that runs on Win32 and the driver is there but not implemented on Win32 you will have make the required configuration changes in config.h and then build ntpd from source and test it. The following reference clock is known to work and is supported by Windows NT: <a href="../drivers/driver1.html">Type 1</a> Undisciplined Local Clock (LOCAL)</p> + <h4>Functions Supported</h4> + <p>All NTP functions are supported with some constraints. See the <a href="#ToDo">TODO list</a> below. Note that the ntptrace executable is not supported and you should use the PERL script version instead.</p> + <h4>Accuracy</h4> + <p>Greg Brackley has implemented a fantastic interpolation scheme that improves the precision of the NTP clock using a realtime thread (is that poetic or what!) which captures a tick count from the 8253 counter after each OS tick. The count is used to interpolate the time between operating system ticks.</p> + <p>On a typical 200+ MHz system NTP achieves a precision of about 5 microseconds and synchronizes the clock to +/-500 microseconds using the <a href="http://www.trimble.com/products/ntp">Trimble Palisade</a> as UTC reference. This allows distributed applications to use the 10 milliseconds ticks available to them with high confidence.</p> + <h4>Binaries</h4> + <p>Recent InstallShield based executable versions of NTP for Windows NT (intel) are available from:</p> + <ul> + <li><a href="http://www.five-ten-sg.com/">http://www.five-ten-sg.com/</a> + </ul> + <h4 id="ToDo">ToDo</h4> + <p>These tasks are in no particular order of priority.</p> + <ul> + <li>Add IPv6 support + <li>See if precision can be improved by using CPU cycle counter for tick interpolation. + <li>Make precision time available to applications using NTP_GETTIME API + </ul> + <h4>Compiling Requirements</h4> + <ul> + <li>Windows 7 or Windows.NET Server 2003, or later. + <li>Windows NT 4.0 Windows 2000, Windows XP or Windows Vista <i>may</i> still work. + <li>Microsoft Visual C++ 2008, 2010, or 2013 EE + <li>Some way of uncompressing and untarring the gzipped tar file. + <li>OpenSSL must be built on the box before building NTP. Additional steps would + be required to not use OpenSSL. + <li>Microsoft Visual C++ redistributables</ul> + <a name="Compiling"><B>Compiling Instructions</B></a> + <ol> + <li>Install Micosoft Visual C++ <a href="http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF">redistributables</a> + <li>Install <a href="http://www.slproweb.com/products/Win32OpenSSL.html">OpenSSL full installer for Windows</a>. Add the following to your system environment variables in the control panel (adjusting paths as appropriate to point to the directory containing only an openssl subdirectory, for OPENSSL_INC, and to the directory containing openssl .lib files for OPENSSL_LIB: +<ul><li> OPENSSL_INC=C:\OpenSSL\include +<li> OPENSSL_LIB=C:\OpenSSL\lib</ul> + <li>Unpack the NTP-4.x.tar.gz using utilities such as WinZip or WinRar. + <li>Run Microsoft Visual C++ 2008 EE. + <li>Open the ports\winnt\vs2008\ntp.sln solution file + <li>Batch build all projects (Build menu, Batch Build..., select all, build). + <li>The built binaries can be found in the <tt>ports\winnt\v2008\Win32-bin\Release</tt> directory. + <li>If you are shipping binaries in a kit it is strongly recommended that you ship this file (winnt.html) along with the binaries. + </ol> + <h4>Configuration File</h4> + <p>The default NTP configuration file path is %SystemRoot%<tt>\system32\drivers\etc\. </tt>(%SystemRoot% is an environmental variable that can be determined by typing "set" at the "Command Prompt" or from the "System" icon in the "Control Panel").</p> + <p>Refer to your system environment and create your<tt> ntp.conf</tt> file in the directory corresponding to your system installation. The older <tt><WINDIR>\ntp.conf</tt> is still supported but you will get a log entry reporting that the first file wasn't found. + <h4>Installation Instructions</h4> + <p>The <tt>instsrv</tt> program in the instsrv subdirectory of the distribution can be used to install 'ntpd' as a service and start automatically at boot time. Instsrv is automatically compiled with the rest of the distribution if you followed the steps above.</p> + <ol> + <li>Start a command prompt and enter "instsrv.exe <pathname_for_ntpd.exe>" + <li>Clicking on the "Services" icon in the "Control Panel" will display the list of currently installed services in a dialog box. The NetworkTimeProtocol service should show up in this list. Select it in the list and hit the "Start" button in the dialog box. The NTP service should start. + <li>You can also stop and start the service by typing net start|stop NetworkTimeProtocol at the DOS prompt. + <li>View the event log by clicking on the "Event Viewer" icon in the "Administrative Tools" group, there should be several successful startup messages from NTP. NTP will keep running and restart automatically when the machine is rebooted. + </ol> + <p>You can change the start mode (automatic/manual) and other startup parameters corresponding to the NTP service in the "Services" dialog box if you wish.</p> + <h4>Removing NTP</h4> + <p>You can also use <tt>instsrv</tt> to delete the NTP service by entering: <tt>>"instsrv.exe remove"</tt> + <h4>Command Line Parameters and Registry Entries</h4> + <p>Unlike the Unix environment, there is no clean way to run 'ntpdate' and reset the clock before starting 'ntpd' at boot time. NTP will step the clock up to 1000 seconds by default. While there is no reason that the system clock should be that much off during bootup if <tt>ntpd</tt> was running before, you may wish to override this default and/or pass other command line directives. + <p>Use the registry editor to edit the value for the ntpd executable under LocalMachine\System\CurrentControlSet\Services\NTP.</p> + <p>Add the -g option to the ImagePath key, behind "%INSTALLDIR>\ntpd.exe". This will force NTP to accept large time errors (including 1.1.1980 00:00)</p> + <h4>Bug Reports</h4> + <p>Please follow the <a href="../bugs.html">NTP Bug Reporting Procedures</a> to report bugs or request enhancements.</p> + <p>Last update: + <!-- #BeginDate format:En2m -->6-Apr-2014 23:27<!-- #EndDate --> + </p> + + </body> +</html> |