From owner-freebsd-hackers Fri Dec 26 18:31:13 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21323 for hackers-outgoing; Fri, 26 Dec 1997 18:31:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21315 for ; Fri, 26 Dec 1997 18:31:07 -0800 (PST) (envelope-from ken@plutotech.com) Received: (from ken@localhost) by pluto.plutotech.com (8.8.7/8.8.5) id TAA27023 for hackers@freebsd.org; Fri, 26 Dec 1997 19:31:05 -0700 (MST) From: Kenneth Merry Message-Id: <199712270231.TAA27023@pluto.plutotech.com> Subject: Re: procedure to adjust clock drift? In-Reply-To: <199712261753.SAA26396@uriah.heep.sax.de> from J Wunsch at "Dec 26, 97 06:53:01 pm" To: hackers@FreeBSD.ORG Date: Fri, 26 Dec 1997 19:31:05 -0700 (MST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk J Wunsch wrote... > Vladimir Litovka wrote: > > >> Calling ntpdate repeatedly in a running system is not a good idea, > >> since it'll cause `time warp's. > > > You can call ntpdate every 1/2 hour, so time warps will be very > > small. About link to the world: I have local NTP-server, which > > sinchronizes with external servers, and set of local stations, which > > sinchronize with my server for reduce load on outgoing link. > > Still, why can't you run xntpd on the clients against your local > server? Apart from some saved virtual memory (for xntpd), i can't > find any advantage in the `run ntpdate every 30 minutes' method. I've got a 486 that won't ever sync up properly with ntp. (i.e. when you do a ntptrace, it always shows itself as stratum 16, etc.) I have to run ntpdate to keep it synced up. Ken -- Kenneth Merry ken@plutotech.com