🚀 go-pugleaf

Sounds like somebody probably recompiled the program while you
weren't looking.
 
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.
 
From ntp-relay@trantor.umd.edu Wed Mar 13 22:16:32 1991
Received: Wed, 13 Mar 91 22:16:28 EST from trantor.umd.edu by merit.edu (5.59/1.6)
Received: by trantor.umd.edu (5.65/1.34)
	id AA14927; Wed, 13 Mar 91 22:04:06 -0500
Received: from merlin.Nersc.gov by trantor.umd.edu (5.65/1.34)
	id AA14922; Wed, 13 Mar 91 22:04:01 -0500
Received: from windsail.nersc.gov by merlin.nersc.gov (4.1/NERSC-1.18a)
	id AA05941; Wed, 13 Mar 91 19:04:12 PST
Received: by windsail.nersc.gov (4.1/SMI-4.1)
	id AA00896; Wed, 13 Mar 91 19:04:06 PST
Date: Wed, 13 Mar 91 19:04:06 PST
From: ramus@windsail.nersc.gov (Joe Ramus)
Message-Id: <9103140304.AA00896@windsail.nersc.gov>
To: ntp@trantor.umd.edu
Subject: NTP & Sparcstation
Status: RO

HELP.  Is there a proper way to stop the xntpd server and then start
it again later?

I have SunOS 4.1 on a Sparc.
I have the latest XNTP stuff from the LOUIE machine.
I built it all and set up a configuration file and had the
server running for more than 24 hours.  It was great.

Then I killed it by:   kill -9 pid

Now it will not run again.  It seems to start and I can do a PS and
see it but then it goes away real soon.  Here is a sample line:

root       871  0.0  4.9   80  332 ?  S <  18:49   0:00 xntpd -c /etc/ntp.conf

I tried rebooting my system but that did not help.
I run the  TICKADJ program.

I tried the NTPQ program and it works.

I also tried NTPDATE  and it gives a message:   Alarm clock

Thanks in advance for any help you can give me.
Joe Ramus  Lawrence Livermore Lab      ramus@nersc.gov