Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!caen!uwm.edu!bionet!agate!ucbvax!es.ele.tue.nl!gjalt
From: gjalt@es.ele.tue.nl (Gjalt de Jong AIO)
Newsgroups: comp.protocols.time.ntp
Subject: Re:  need help with ntpd
Message-ID: <9103210740.AA04434@es.ele.tue.nl>
Date: 21 Mar 91 07:40:28 GMT
References: <9103201810.AA00909@kahala.soest.hawaii.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 23


on Wed, 20 Mar 91 08:10:51 HST,
bob@kahala.soest.hawaii.edu (Bob Cunningham) said:


> Alliant machines have strange Unix kernels due to their multiprocessing
> configurations (two different types of cpus; an FX machine can have
> several of each).  In brief, ntpd from the ntp.3.4 distribution just
> doesn't work (nor ntpd from any previous distribution).  Nor xntpd.  A
> couple of years ago I tried digging in and trying to find out why, but
> finally gave up after exhausting my (admittedly meager) knowledge of
> the unique internels of the Alliant kernels.

> The only good news I have for you is that "ntpdate" (from the xntp
> distribution) apparently works just fine.  I've been running that on

How strange. We have xntpd running on our Alliant FX/8 without any problems.
No compilation problems and it also runs fine.
__
Gjalt G. de Jong,                 | Phone: +31-40-473345, Fax. +31-40-448375
Eindhoven University of Technology, Dept. of Electr. Eng. (ES/EH 7.26)
P.O. Box 513, 5600 MB Eindhoven, The Netherlands
Email: gjalt@es.ele.tue.nl