From owner-freebsd-hackers Fri Dec 26 08:56:35 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA20582 for hackers-outgoing; Fri, 26 Dec 1997 08:56:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from grunt.vl.net.ua (grunt.vl.net.ua [193.124.76.209]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA20318 for ; Fri, 26 Dec 1997 08:50:15 -0800 (PST) (envelope-from news@grunt.vl.net.ua) Received: from news by grunt.vl.net.ua with local (Exim 1.73 #1) id 0xlcpU-0003Rc-00; Fri, 26 Dec 1997 18:41:44 +0200 To: freebsd-hackers@FreeBSD.ORG Subject: Re: procedure to adjust clock drift? Date: 26 Dec 1997 18:41:44 +0200 Message-ID: <680mo8$ctn$1@grunt.vl.net.ua> X-Newsreader: TIN [UNIX 1.3 unoff BETA 970930; i386 FreeBSD 2.2.5-STABLE] X-Via: News-To-Mail v1.0 From: Vladimir Litovka Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk In maillist.freebsd.hackers J Wunsch wrote: > If you've got an NTP server at your reach, the idea is that you call > ntpdate at boot-time, and run xntpd to stay in sync afterwards. > 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. -- Vladimir Litovka , hostmaster of vl.net.ua ---------------- Don't trouble trouble until trouble troubles you