Path: utzoo!attcan!uunet!snorkelwacker!usc!zaphod.mps.ohio-state.edu!math.lsa.umich.edu!math.lsa.umich.edu!emv From: emv@math.lsa.umich.edu (Edward Vielmetti) Newsgroups: comp.protocols.time.ntp Subject: Re: setting time Message-ID: Date: 20 Sep 90 00:40:00 GMT References: <125@cheltenham.cs.arizona.edu> Sender: usenet@math.lsa.umich.edu Organization: University of Michigan Math Dept., Ann Arbor MI. Lines: 21 In-Reply-To: ric@cs.arizona.edu's message of 19 Sep 90 21:27:17 GMT In article <125@cheltenham.cs.arizona.edu> ric@cs.arizona.edu (Ric Anderson) writes: I have worked around this on the Sun systems, by doing an rdate before starting ntp, but this doesn't seem right. On the other machines, I don't have a workaround. How does one make ntpd set the clock initially? I just set up some Ultrix machine according to the Ultrix 4.0 documentation, which suggests that you do a routine like rdate -s ntp -f -s server1 server2 server3 ntpd -n in that order; the first one should get you to the right hour, the second reasonably close like to about a second, and finish things off with ntpd which should then sync pretty quickly. --Ed Edward Vielmetti, U of Michigan math dept