HDTenEightyP/NetNews huggingface dataset:
From: matt@wardsgi.med.yale.edu (Matt Healy)
Subject: Re: Bell of PA
Followup-To: comp.protocols.time.ntp
Organization: Yale U. - Genetics
Date: Wed, 16 Dec 1992 19:17:58 GMT

In article <1992Dec15.161155.4773@fccc.edu>, stodola@orion.fccc.edu (Robert
K. Stodola) wrote:
> 
> This is probably a FAQ question, but...
> 
> When I first put up NTP (a long time ago), I noted that Bell of PA time was
> two seconds faster than my computers time.  Today its off by the same two
> seconds.  One of them is obviously very reliably wrong (I lean towards
> Bell).  It does seem rather curious, especially since its fast rather than
> slow, which might be explained by other types of delays.
> 
> I know the phone company would probably tell me that in a disagreement between
> reality and Bell, they are definitive, but if anyone has an explanation of
> this phenomena, I'd like to hear it.
> 
> -- 
> 
> stodola@fccc.edu -- Robert K. Stodola (occasionally) speaks for himself.

Welcome to the wonderful world of highly accurate time!  The
Internet document RFC 1305 -- which defines Network Time
Protocol -- has an extensive discussion of the things that
can go wrong with time services.  Yale's campus network time
server frequently drifts a bit, too -- right now it is off by
about 1 second.  Local phone companies can be even worse.

Personally, I rely most on my el cheapo wristwatch, which
I *know* gains about 0.093 seconds per day.  I check it
fairly frequently against the NIST clock (available on
various frequencies with a shortwave radio, or you can
phone 303-499-7111).

About once a week I do a linear regresion of error versus
day of the year for the past 6 months, discard all values
that are off by more than 0.6 second, and recompute the
regression line.  This way I am confident I always *know*
the time to within +/- 0.25 second.  Theoretically computers
"should" be able to do better than 0.25 second, but I've yet
to encounter any that do.

[for those who may be curious: It is a CASIO F-24W for which
 I paid 15 dollars ca. 5 years ago.  I have never even replaced
a battery, and it has never to my knowledge deviated significantly
from the 0.093 second per day rate I quoted above.  The
packaging claimed the lithium battery was good for 7 years.]


Matt Healy
"I pretend to be a network administrator;
 the lab net pretends to work"

matt@wardsgi.med.yale.edu
From: nicinski@fndaud.fnal.gov (Tom Nicinski)
Newsgroups: comp.protocols.time.ntp
Subject: VxWorks NTP: MVME167 problem (Prev time adj didn't complete)
Date: 14 Dec 1992 16:37:51 GMT
Organization: Fermi National Accelerator Laboratory, Batavia IL
Distribution: world
NNTP-Posting-Host: fndaud.fnal.gov
Keywords: VxWorks MVME167

I'm using the VxWorks port of NTP on both a Motorala MVME147 and MVME167.  I've
gotten the 147 to work reasonably well.  But, on the 167, after 15 minutes or
so, I constantly get:

    Previous time adjustment didn't complete

Since I'm not familiar with NTP, has anyone else seen this problem and solved
it.  Our clock rate is 1000 Hz on both machines.  NTPD is the only "user" task
operating on the machines (during our NTP tests), so there's nothing really to
steal the CPU away from timekeeping.
Newsgroups: comp.protocols.time.ntp
From: peppe@ipgaix.unipg.it (G. Vitillaro)
Subject: xntpd and timed
Summary: Have timed to be stopped before to start xntpd?
Keywords: xntpd, timed
Organization: Universita' di Perugia
Date: Thu, 17 Dec 1992 14:54:34 GMT

We are currently using <timed> on our (still little,
but growing) network. We are planning to start to use 
xntpd.

May I suppose that I have to stop timed on all the machines
where I'm going to start xntpd? May they coexist in some way?

Thank in advance for any help or suggestion,

Regards  G. Vitillaro
-- 
Giuseppe Vitillaro - IBM SEMEA      |  E-Mail : peppe@ipgaix.unipg.it 
University of Perugia Italy         |  06100 Perugia  Phone:+39.75.585-2200
---------------------------------------------------------------------------
All comments/opinions are mine and don't represent those of IBM
Newsgroups: comp.protocols.time.ntp
From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
Subject: Re: xntpd and timed, etc
Followup-To: comp.protocols.time.ntp
Organization: Naval Research Laboratory, DC
Distribution: na
Date: Fri, 18 Dec 1992 19:51:57 GMT

In article <1992Dec18.175438.16954@Arco.COM> Matt Mannhardt <lasmtm@Arco.COM> writes:

% Then the DEC Sys Admin boys found out that NTP version 1 was also
% readily availible in Ultrix and that the Internet gateway at our
% sister-division was a stratum 2 ntp server.  They broke off this
% summer and went with 'ntpd' instead of 'timed'.  This didn't hurt too
% much as there is no NFS to/from the DEC's and the other UNIX
% platforms.

  NTP version 1 is really old.  They should upgrade from using ntpd(8)
to using xntpd(8) using the freely distributable sources available via
anonymous ftp from /pub/ntp on louie.udel.edu (the official xntp3
archive site).
 
>AIX doesn't have that timed option and HP/UX doesn't even have a 'timed'.  
>I have yet to hit up "the gopher and archie" to see what 'timed' 
>source is availible.

  I know that xntp3 has been ported to AIX machines because the
University of Virginia is running xntp3's xntpd(8) on their AIX
RS/6000 machines.  I assume it compiles "out of the box" but haven't
checked that personally since I have no AIX machines myself.  It does
compile out of the box and run fine on HPUX-based HP 700 systems.  I
haven't tried it under HP's B1-targeted operating system but might if
time permits during 1993 (I expect it will be tricky to port with
least privilege because of BLS kernel permissions and other MAC issues).

  I'd recommend migrating all of the machines to using the xntpd from
the xntp3 distribution.  I've migrated all but one of the machines in
my area of the lab to xntp3 and have talked several other parts of the
lab into using xntp3 as well.  

  Having really accurate time turns out to be essential in networking
research (and probably also is helpful in debugging networks) because
you can time correlate various events on the research (or operational)
network to help figure out how things are behaving and interacting.
It also is essential to get accurate performance measures.

Ran
atkinson@itd.nrl.navy.mil
Newsgroups: comp.protocols.time.ntp
From: wales@CS.UCLA.EDU (Rich Wales)
Newsgroups: comp.protocols.time.ntp
Subject: Reminder of NTP change at UCLA
Date: 18 Dec 92 00:50:51 GMT
Distribution: inet
Organization: The Internet

I announced the following change about a month ago and included a new
paragraph for the "clock.txt" file, but apparently it got lost in the
shuffle, so here goes again:

    delphi.cs.ucla.edu (131.179.128.36)
    Location: UCLA Computer Science Department, Los Angeles, CA
    Geographic Coordinates: 34:04:08N, 118:26:31W
    Synchronization: NTP secondary (stratum 2), SPARC/UNIX
    Service area: NSFNET, SDSC region
    Access policy: open access
    Contact: ops@cs.ucla.edu
    Note: Old hosts (ntp1,ntp2).cs.ucla.edu are no longer in service.
	  Please access Delphi from at most one host at your site.

Please note that the above should =replace= the existing info for the
hosts ntp1.cs.ucla.edu and ntp2.cs.ucla.edu.  Anyone who is still trying
to chime with these old hosts is just wasting network bandwidth.

Also, please note the new contact address (an alias for our facility
operations staff).  I am leaving UCLA at the end of the month and will
be moving to Canada to begin a new job with Mortice Kern Systems (MKS)
in Waterloo, Ontario (west of Toronto).

Rich Wales <wales@CS.UCLA.EDU> // UCLA Computer Science Department
3531 Boelter Hall // Los Angeles, CA 90024-1596 // +1 (310) 825-5683
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.time.ntp
Subject: Re:  Trouble polling internet
Date: 18 Dec 92 06:11:20 GMT
Distribution: inet
Organization: The Internet

Debbie,

For the archives on louie.udel.edu use login anonymous and password
your grandmother's maiden name.

Dave
From: sanjay@SAATHI.NCST.ERNET.IN
Newsgroups: comp.protocols.time.ntp
Subject: assistance for selecting a peer..
Date: 17 Dec 92 09:05:35 GMT
Distribution: inet
Organization: The Internet


Hello,

I am from ERNET ( Educational and Research Network ), India. I have put
ntp, ntpd and ntpdc on a Sun Sparc 1+ which acts as the gateway for all
ERNET sites. I would like the ntpd to redistribute time to other ERNET
sites in Delhi, Bangalore and Madras. Please tell me which ntp peer to
use.

Also I need some help in configuring ntp here. In case you do not handle
this I will appreciate if you will forward this query to the right
person. The info. I need is:

1) How to modify the tickadj parameter in the kernel. What I am looking
for is the file which will have this. The kernel files do not have a
"conf.c". Could you suggest which file will have this?

2) To configure a reference clock in /etc/ntp.conf what will be the
device?

Thanks in advance,

Sanjay
sanjay@saathi.ncst.ernet.in
From: rbthomas@frogpond.rutgers.edu (Rick Thomas)
Newsgroups: comp.protocols.time.ntp
Subject: Re:  Trouble polling internet
Date: 19 Dec 92 16:23:44 GMT
Distribution: inet
Organization: Rutgers Engineering Supercomputer Lab

# >For the archives on louie.udel.edu use login anonymous and password
# >your grandmother's maiden name.
# >
# >Dave
# 
# Paternal or maternal?

Either will be accepted.  It's realy quite smart about that (8->).
Newsgroups: comp.protocols.time.ntp
From: bogstad@blaze.cs.jhu.edu (Bill Bogstad)
Subject: xntpd: Previous time adjustment didn't complete
Organization: Johns Hopkins Computer Science Department, Baltimore, MD
Date: Fri, 11 Dec 1992 21:13:27 GMT

	I just installed the xntpd(3) daemon on a Sun running OS 4.1.1 and
I'm getting periodic syslog messages like the following:

Dec 11 16:05:00 blaze xntpd[8339]: Previous time adjustment didn't complete

Can somebody suggest to me what the problem is?  Also, when I start up xntpd
I get a single message about being unable to open /dev/pps.  I configured
the xntpd suite without any support for reference clocks.  (This required a
minor change to xntpd/ntp_loopfilter.c in order to compile and link
successfully.)

				Thanks,
				Bill Bogstad
From: paul@uxc.cso.uiuc.edu (Paul Pomes - UofIllinois CSO)
Newsgroups: comp.protocols.time.ntp
Subject: xntpd and ntpdate don't work under Dynix (Sequent)
Date: 13 Dec 92 16:42:45 GMT
Article-I.D.: news.Bz7IFA.GxM
Reply-To: Paul-Pomes@uiuc.edu
Organization: University of Illinois at Urbana

After some poking around it seems the cause is explained in the fcntl(2)
man page:

BUGS
     The asynchronous I/O facilities of FNDELAY and FASYNC are
     currently available only for tty operations.

Is there a work-around?  Fixing Dynix really isn't an option as Sequent
is no longer developing it in favor of Dynix/ptx.  We do have a source
license if a kernel fix is the only way to go.

/pbp
-- 
Necessity is the argument of tyrants, it is the creed of slaves.
	--William Pitt (1783)
Newsgroups: comp.protocols.time.ntp
From: mrapple@quack.sac.ca.us (Nick Sayer)
Subject: FAQ (was Re: xntpd: Previous time adjustment didn't complete)
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
Date: 13 Dec 1992 17:00:12 UTC

rbthomas@frogpond.rutgers.edu (Rick Thomas) writes:

>If there were a FAQ for this group, this would be on it.

I'm making one up. Suggestions are welcome. I'll post it in a bit.

-- 
Nick Sayer <mrapple@quack.sac.ca.us> | 
N6QQQ @ N0ARY.#NOCAL.CA.USA.NOAM     | "I am not a number! I am a free man!"
37 19 49 N / 121 57 36 W             | 
+1 408 249 9630, log in as 'guest'   |                 -- Number 6
From: matthew@WOODY.JPL.NASA.GOV (Matthew McGillis)
Newsgroups: comp.protocols.time.ntp
Subject: xntpd version 3.1
Date: 13 Dec 92 19:03:52 GMT
Distribution: inet
Organization: The Internet


	I have been running xntpd version 3.1 on sun sparcs and have
	noticed that trying to use the internal clock with this version
	does not work.  If I set a machine to sink to its internal clock
	at let say strat 5 that machine will not then broadcast itself
	as a strat 5 clock instead it thinks it is strat 18 or 21 (I
 	forget what the exact number is but its the highest possible).
	Because of this when I loose my network connection all my machine
	clocks start to slowly wonder.  Can you give me any clues as
	to if I'm doing something wrong or if this is a bug.  I have used
	xntpd version 2?? in the past and have not seen this problem.
From: owen@astro.washington.edu (Russell Owen)
Newsgroups: comp.protocols.time.ntp
Subject: Datum GPS clocks--are they any good?
Date: 14 Dec 92 23:31:52 GMT
Article-I.D.: rowen.owen-141292151616
Followup-To: comp.protocols.time.ntp
Distribution: na
Organization: University of Washington

We're looking for a good GPS receiver clock that has:
- an RS-232 output
- a 1 pulse-per-second output
- can output GPS time (similar to UTC but no leap seconds)
additional nice features would be:
- an ovenized internal oscillator (in case our antenna is struck by
lightning)
- as few controls as possible (less to get screwed up by button-pushers)
- rack mount

So far the best bet appears to be a $4000 model from Datum, the 9390-5200.
It seems to do everything we want and has no front panel controls at all!

We have also looked at offerings from Odetics and TrueTime. The Odetics
clocks would be the best bet, but they cannot output GPS time. TrueTime has
quite a variety of clocks, but at present no cheap simple clocks (though
some are due out shortly--not rack-mount).

So...has anyone used a clock from Datum, Inc.? Did you like it? Any
comments on TrueTime or other alternative companies? Note: I have already
read the excellent file pub/ntp/doc/clocks.txt from louie.udel.edu.

I will summarize any e-mail responses. Any help or advice would be most
appreciated.

Russell Owen
owen@astro.washington.edu
Astronomy Dept. FM-20
University of Washington
Seattle, WA 98195
206-543-2859
From: ranck@joesbar.cc.vt.edu (Wm. L. Ranck)
Newsgroups: comp.protocols.time.ntp
Subject: Re: Bell of PA
Date: 16 Dec 92 20:57:09 GMT
X-Newsreader: TIN [version 1.1 PL6]

Robert K. Stodola (stodola@orion.fccc.edu) wrote:
: seconds.  One of them is obviously very reliably wrong (I lean towards

There is an old proverb that goes something like this:  A man with a clock
knows what time it is, but a man with two clocks is never sure.
--

*******************************************************************************
* Bill Ranck                                          ranck@joesbar.cc.vt.edu *
* Computing Center at Virginia Tech, not Vermont ----------------------^^     *
*******************************************************************************
From: stodola@orion.fccc.edu (Robert K. Stodola)
Newsgroups: comp.protocols.time.ntp
Subject: Bell of PA
Date: 15 Dec 92 16:11:55 GMT
Organization: Fox Chase Cancer Center

This is probably a FAQ question, but...

When I first put up NTP (a long time ago), I noted that Bell of PA time was
two seconds faster than my computers time.  Today its off by the same two
seconds.  One of them is obviously very reliably wrong (I lean towards
Bell).  It does seem rather curious, especially since its fast rather than
slow, which might be explained by other types of delays.

I know the phone company would probably tell me that in a disagreement between
reality and Bell, they are definitive, but if anyone has an explanation of
this phenomena, I'd like to hear it.

-- 

stodola@fccc.edu -- Robert K. Stodola (occasionally) speaks for himself.
Newsgroups: comp.protocols.time.ntp
From: peppe@ipgaix.unipg.it (G. Vitillaro)
Subject: xntp3 certification
Keywords: xntp3, AIX/6000, AIX/370
Organization: Universita' di Perugia
Date: Wed, 16 Dec 1992 22:44:19 GMT

I just finished to compile (following the indication)
xntp3 for AIX/6000 3.1.5 and AIX/370 1.2.1 (lev 1400).

I would like to know if exist some standard methods
to certify that xntp work fine on a machine (expecially
for AIX/370 where I didn't find any Config file).

I tried ntpq with a Stratum 1 (in Swiss) and it seems
to work, but I think that xntpd is another question.

Any "easy" way to test the package that just not
"try and go"?

Thank in advance, G. Vitillaro
-- 
Giuseppe Vitillaro - IBM SEMEA      |  E-Mail : peppe@ipgaix.unipg.it 
University of Perugia Italy         |  06100 Perugia  Phone:+39.75.585-2200
---------------------------------------------------------------------------
All comments/opinions are mine and don't represent those of IBM
From: peppe@ipgaix.unipg.it (G. Vitillaro)
Newsgroups: comp.protocols.time.ntp
Subject: xntp3 under AIX/370 1.2.1 (PL 1400)
Summary: xntpd hangs under AIX/370 1.2.1 (1400)
Keywords: AIX/370, xntp3, hang
Date: 20 Dec 92 21:25:04 GMT
Organization: Universita' di Perugia

I'm trying to run xntp3 under AIX/370 1.2.1 (PL 1400).

I know that this system is going, but we will have it here
at least for the next six months here and I would like to run
xntpd under it.

I compiled xntpd succesfully (so seem at least), but it seems
to hang. What I can see is that it seems that xntpd is
not receiveing any packet or at least <getrecvbufs> is
always called without anything to do.

More I tried ntpq and xntpdc with other servers and they
work but I cannot obtain any answer from the xntpd running
under AIX/370 (both from the same host than from others).

I compiled xntpd with bsdcc (it is anologous to the one in
AIX/6000: BSD compatibility include files and libs at
the level 4.3 I believe).

One of major doubt is about the fact that xntpd use ASYNC
I/O on udp socket by default. I'm not completely sure AIX/370
can handle them (fcntl man page is not completely clear at
this purpose). I tried to compile xntpd with -DUSESELECT
(as for the Sequent), but it answer to the first few packets,
the hangs again.

So now I'm out of hope: I don't know so deeply udp sockets
to extensively debug xntpd. 

One last think: I tried to define -DNODETACH (I saw something
in ntpd.c suggesting this for Apollo). Same result: hang.

I hope someone in the Network may have better advice than me,
or maybe I'm so lucky someone else already compiled xntpd
for AIX/370 (I don't hope that so much).

If someone "solved" a similar problem for other platforms
and gan give some hint I will be forever gratfully to him.

Regards  G. Vitillaro
-- 
Giuseppe Vitillaro - IBM SEMEA      |  E-Mail : peppe@ipgaix.unipg.it 
University of Perugia Italy         |  06100 Perugia  Phone:+39.75.585-2200
---------------------------------------------------------------------------
All comments/opinions are mine and don't represent those of IBM

-- 
Giuseppe Vitillaro - IBM SEMEA      |  E-Mail : peppe@ipgaix.unipg.it 
University of Perugia Italy         |  06100 Perugia  Phone:+39.75.585-2200
---------------------------------------------------------------------------
All comments/opinions are mine and don't represent those of IBM
From: rbthomas@frogpond.rutgers.edu (Rick Thomas)
Newsgroups: comp.protocols.time.ntp
Subject: Re: xntpd: Previous time adjustment didn't complete
Date: 13 Dec 92 06:05:42 GMT
Organization: Rutgers Engineering Supercomputer Lab



> 	I just installed the xntpd(3) daemon on a Sun running OS 4.1.1 and
> I'm getting periodic syslog messages like the following:
> 
> Dec 11 16:05:00 blaze xntpd[8339]: Previous time adjustment didn't complete
> 
> 				Thanks,
> 				Bill Bogstad

If there were a FAQ for this group, this would be on it.

First, check and make sure you have turned off "dosynctodr".  You can
do that with  "tickadj -s" in /etc/rc.local, or you can fix it in /vmunix
with adb.

Second, if that doesn't fix it, request your Sun field support to
install the latest level of boot proms (at least level 2.4)  This fixes
a problem with clock interrupts getting lost when large volumes of text
are sent to the raw (non window-managed) console screen.  (It doesn't
really fix the problem, but it reduces it to a manageable level.)

Enjoy!

Rick
========================================================================
Rick Thomas, Manager
Supercomputer Remote Access Center, Rm B113
Rutgers University, College of Engineering
Brett and Bowser Roads
Piscataway, NJ 08855-0909

Phone: (908) 932-4301
Fax:   (908) 932-5313
Internet: rbthomas@jove.rutgers.edu
UUCP: {any backbone site}!rutgers!rbthomas
========================================================================
Newsgroups: comp.protocols.time.ntp
From: gp@cunixf.cc.columbia.edu (Gerald Pulver)
Subject: Re:  Trouble polling internet
Reply-To: gp@cunixf.cc.columbia.edu (Gerald Pulver)
Organization: Columbia University
Distribution: inet
Date: Fri, 18 Dec 1992 17:40:28 GMT

In article <9212180111.aa20559@huey.udel.edu> Mills@UDEL.EDU writes:
>Debbie,
>
>For the archives on louie.udel.edu use login anonymous and password
>your grandmother's maiden name.
>
>Dave

Paternal or maternal?
From: sanjay@SAATHI.NCST.ERNET.IN
Newsgroups: comp.protocols.time.ntp
Subject: assistance for selecting a peer..
Date: 8 Dec 92 09:35:12 GMT
Distribution: inet
Organization: The Internet

Hello,

I am from ERNET ( Educational and Research Network ), India. I have put
ntp, ntpd and ntpdc on a Sun Sparc 1+ which acts as the gateway for all
ERNET sites. I would like the ntpd to redistribute time to other ERNET
sites in Delhi, Bangalore and Madras. Please tell me which ntp peer to
use.

Also I need some help in configuring ntp here. In case you do not handle
this I will appreciate if you will forward this query to the right
person. The info. I need is:

1) How to modify the tickadj parameter in the kernel. What I am looking
for is the file which will have this. The kernel files do not have a
"conf.c". Could you suggest which file will have this?

2) To configure a reference clock in /etc/ntp.conf what will be the
device?

Thanks in advance,

Sanjay
sanjay@saathi.ncst.ernet.in
Newsgroups: comp.protocols.time.ntp
From: art@cs.UAlberta.CA (Art Mulder)
Subject: xntp3, mips: strange messages in /usr/adm/messages
Summary: xntpd producing umpteen bazillion entries in /usr/adm/messages
Keywords: xntp3 mips messages 
Organization: University of Alberta, Edmonton, Canada
Date: Mon, 14 Dec 1992 20:54:52 GMT


Hello xntp experts!

  I have installed xntp3 throughout our department, and it seems
  to be acting up on two of our three mips.  (It runs fine on the
  Suns and Dec's---so far)

  On the mips 3230 everything seems to be under control, but on
  the mips M1000 (RISC/os 4.52) I get messages like this in the
  /usr/adm/messages file:
      xntpd[231]: peer 129.128.28.101 event 84 status 1014
      xntpd[231]: peer 129.128.23.12 event 84 status 1014

  The mips M120 (RISC/os 4.51) produces similary messages, and 
  a different one:
    xntpd[122]: peer 129.128.4.11 event 84 status 90f4
    xntpd[122]: peer 129.128.4.39 event 84 status 90f4
    xntpd[122]: peer 129.128.72.39 event 84 status 1014

    xntpd[122]: adjust: STEP dropped (129.128.4.240 offset 0.  187578321)
    xntpd[122]: adjust: STEP dropped (129.128.4.240 offset 0.  214247108)

  At bootup, the following commands are executed:
    /usr/etc/ntpdate host1 host2 host3 host4
    /usr/etc/xntpd

  The time still seems to be kept accurate, and I can't find anything about
  this in the manual, but the sheer number of these messages getting
  dropped into /usr/adm/messages concerns me.  

  Please email any suggestions or advice.
  Thanks!
--
 ...art mulder ( art@cs.ualberta.ca )    | "Do not be conformed to this world,
 Department of Computing Science         |  but be transformed by the renewal
 University of Alberta, Edmonton, Canada |  of your mind, ..."  Romans 12:2
Newsgroups: comp.protocols.time.ntp