Article 7922 of comp.protocols.time.ntp:
Path: matra.meer.net!news.spies.com!nntp1.jpl.nasa.gov!news.magicnet.net!nntp.newsfirst.com!nntp.crosslink.net!news.inc.net!uwm.edu!rutgers!dziuxsolim.rutgers.edu!igor.rutgers.edu!lilypad.rutgers.edu!not-for-mail
From: rbthomas@lilypad.rutgers.edu (Rick Thomas)
Newsgroups: comp.protocols.time.ntp
Subject: Re: Weird behaviour with xntpd 5.86 under BSD/OS 2.1
Date: 22 Jan 1997 16:39:13 -0500
Organization: Rutgers University LCSR
Lines: 29
Distribution: inet
Message-ID: <5c61e1$jvh@lilypad.rutgers.edu>
References: <5c2luf$7mq@valhalla.comshare.com>
NNTP-Posting-Host: lilypad.rutgers.edu
Cc: rbthomas
Xref: matra.meer.net comp.protocols.time.ntp:7922

mikep@valhalla.comshare.com (Michael Pelletier) writes:
		<majorly snipped for brevity>

> It almost seems like there's
>some other something adjusting the clock behind xntpd's back.

Is "timed" running on your machine?  Does the OS default to trying to
sync its software real-time-clock to the machine's hardware Time-of-Day clock?
Either of these could cause what you are seeing.

>There's also nothing in syslog.  Does anyone have suggestions on what
>kind of ntp.conf logging to turn on to try to track down the problem
>here?  Thanks!

I put 

	logconfig all

in my ntp.conf file, and 

	daemon.debug    /var/adm/debug.log

in my syslog.conf file.

I believe this gives me all the logging info there is to get.

>	-Mike Pelletier.

Rick