Path: utzoo!news-server.csri.toronto.edu!rutgers!ucsd!ucbvax!WINDSAIL.NERSC.GOV!ramus
From: ramus@WINDSAIL.NERSC.GOV (Joe Ramus)
Newsgroups: comp.protocols.time.ntp
Subject: Re:  NTP & Sparcstation
Message-ID: <9103141838.AA02610@windsail.nersc.gov>
Date: 14 Mar 91 18:38:56 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 25

Thanks to those who helped solve my problem.
I had  xntpd  running once but then it would not run after a reboot.

The problem is that the Sparc has both a BSD & a System V development
environment.  Since I work with System V, I had my path set that way
yesterday when I recompiled the xntpd program.  The earlier version
that worked must have been compiled with my path set for BSD.

So I changed the line in the Config file to look like this:
COMPILER= /usr/ucb/cc

NOTE:  How about mentioning in the README file that SUN machines
       require the use of the BSD environment.
---------------------------------------------------------------------------

>> I get the same "alarm clock" message from ntpdate when I comple
>> on an RS/6000 without the bsd compatibility library.  Perhaps
>> some bad library routines got linked in?  Check the last change
>> date on xntpd.
>>  >> 
>> You've compiled your xntp stuff with /usr/5bin/cc. Use /usr/bin/cc instead.
>> signal(2) works in different ways on System V and BSD systems.
>> System V resets the signal handler (in most cases), BSD does not.

>> Joe Ramus  Lawrence Livermore Lab      ramus@nersc.gov