Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!ucdavis!quack!mrapple From: mrapple@quack.sac.ca.us (Nick Sayer) Newsgroups: comp.protocols.time.ntp Subject: Re: Problem with xntp 1.3 on Suns Message-ID: Date: 21 Jun 91 04:28:36 GMT References: <3834@kraftbus.cs.tu-berlin.de> <1991Jun20.225047.16020@sol.acs.unt.edu> Organization: The Duck Pond, Stockton, CA Lines: 20 mstgil@sol.acs.unt.edu (Marc Ph. A. J. St.-Gil) writes: >net@opal.cs.tu-berlin.de (Oliver Laumann) writes: >> xntpd: Previous time adjustment didn't complete >We solved this by using "tickadj -s -A" before invoking xntp in our rc.local. >The important thing being that -s causes dosynctodr to be turned off in the >kernel. That doesn't solve the problem completely. I made the equivalent modification to the kernel, and I still get that message when the system gets REALLY busy. This is a problem in SunOS. Just ignore it. -- Nick Sayer | Official Scapegoat for the | "And now my mrapple@quack.sac.ca.us | MC68HC11 Mailing List. | post is done!" N6QQQ | To subscribe, send mail to | --buster@acme.edu 209-952-5347 (Telebit) | mc68hc11-request@quack.sac.ca.us |