From owner-freebsd-questions@FreeBSD.ORG Tue Jun 29 09:15:35 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E865A16A4CE for ; Tue, 29 Jun 2004 09:15:35 +0000 (GMT) Received: from auk1.snu.ac.kr (auk1.snu.ac.kr [147.46.100.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87F5943D53 for ; Tue, 29 Jun 2004 09:15:35 +0000 (GMT) (envelope-from stopspam@users.sourceforge.net) Received: from [147.46.44.181] (stopspam@users.sourceforge.net) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004062918:15:01:316010.24099.3045211056 for ; Tue, 29 Jun 2004 18:15:01 +0900 (KST) Message-ID: <40E13322.4070201@users.sourceforge.net> Date: Tue, 29 Jun 2004 18:15:14 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <40E0C929.4090401@users.sourceforge.net> In-Reply-To: <40E0C929.4090401@users.sourceforge.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:1.71) (by Terrace) Subject: Re: FreeBSD cluster: ntpd does not sync time properly? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2004 09:15:36 -0000 Rob wrote: > > Hello, > > I have a FreeBSD cluster, all PCs running FreeBSD-Stable (as of > one week ago). The cluster has a master, connected to the Internet, > and the master is also router, caching nameserver and timeserver > for the internal network. > The master has two internet cards, and there are 6 slaves > on the internal network. > > Problem is, that as time goes on, the system time on master > and slaves deviate more and more. > > Here is my configuration for the time server configuration: > > on MASTER (192.168.0.100) > rc.conf: > ntpdate_enable="YES" > ntpdate_flags="-b time.kriss.re.kr time.nuri.net" > xntpd_enable="YES" > ntp.conf: > # prohibit general access to this service > restrict default ignore > # allow hosts on the 192.168.0.0/24 subnet to query this server > restrict 192.168.0.0 mask 255.255.255.0 nomodify notrap > # localhost has full access to the server > restrict 127.0.0.1 > server time.kriss.re.kr prefer > server time.nuri.net > driftfile /etc/ntp.drift > > > on SLAVE (192.168.0.) > rc.conf: > ntpdate_enable="YES" > ntpdate_flags="-b 192.168.0.100" > xntpd_enable="YES" > ntp.conf: > # prohibit general access to this service > restrict default ignore > # localhost has full access to the server > restrict 127.0.0.1 > server 192.168.0.100 > driftfile /etc/ntp.drift > > > The idea is that at boot-up, time is instantly synchronized once by > unsing "ntpdate -b"; after that ntpd will control time adjustments. > > Am I making a mistake in this setup? Found the solution myself. I should use timed on the internal network, instead of ntpd deamon. That seems to work fine. R.