Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!pipex!marble.uknet.ac.uk!mcsun!Germany.EU.net!ira.uka.de!smurf.sub.org!news From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: comp.os.386bsd.bugs Subject: Re: problems with clock? Date: 31 Mar 1993 17:09:40 +0200 Organization: University of Karlsruhe, FRG Lines: 26 Message-ID: <1pcc7k$l0n@smurf.sub.org> References: <C4q062.4Iv@veda.is> <C4q3B4.159@kithrup.com> <1pb5mk$12lv@hal.gnu.ai.mit.edu> In comp.os.386bsd.bugs, article <1pb5mk$12lv@hal.gnu.ai.mit.edu>, mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes: > > In article <C4q3B4.159@kithrup.com> sef@kithrup.com (Sean Eric Fagan) > writes: > } > } I'm talking about doing something like: > } ntp -s <somereliablesite> > } and then, later, doing > } ntp <thatsamesite> > } > Huh? This sounds like a bug in your implementation of `ntp'. I use > `xntp' version 3, which you can get from: > Assuming that an "ntp", immediately following the "ntp -s", shows no such discrepancy, and also assuming that nothing else changes the clock (like timed, ntpd, ...), a bug in ntp is _very_ unlikely to be the reason for this problem. -- "Aren't you dead?" [James T. Kirk --- Star Trek II: "The Wrath Of Khan"] -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\ Humboldtstrasse 7 -- 7500 Karlsruhe 1 -- Germany -- +49-721-9612521 \o)/