From owner-freebsd-questions@FreeBSD.ORG Tue Jul 1 17:23:01 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92AC11065686 for ; Tue, 1 Jul 2008 17:23:01 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id 66F498FC25 for ; Tue, 1 Jul 2008 17:23:01 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTPSA id 63205EBC08; Tue, 1 Jul 2008 13:23:00 -0400 (EDT) Date: Tue, 1 Jul 2008 13:21:53 -0400 From: Bill Moran To: B. Cook Message-Id: <20080701132153.650e302a.wmoran@potentialtech.com> In-Reply-To: <0911AC74-A73F-4F8B-8495-1FF2DC959B65@poughkeepsieschools.org> References: <0911AC74-A73F-4F8B-8495-1FF2DC959B65@poughkeepsieschools.org> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: OpenNTPd howto? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 17:23:01 -0000 In response to B. Cook : > Hello All, > > Not sure what I am missing, but I am. > > so I put openntpd on a machine (10.20.0.16) > > cat ntpd.conf | egrep -v ^# > > listen on 0.0.0.0 > server clock.nyc.he.net > > then start it and it looks like it does: > > USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN > ADDRESS > _ntp ntpd 15751 4 udp4 10.20.0.16:55180 > 209.51.161.238:123 > _ntp ntpd 15751 6 udp4 *:123 *:* > > > Strange thing one: > > root@core [/usr/local/etc]# 30 > ntpdate -b clock.nyc.he.net > 1 Jul 12:43:52 ntpdate[48881]: the NTP socket is in use, exiting > > root@core [/usr/local/etc]# 31 > /usr/local/etc/rc.d/openntpd stop > Stopping openntpd. > > root@core [/usr/local/etc]# 32 > ntpdate -b clock.nyc.he.net > 1 Jul 12:49:57 ntpdate[70917]: step time server 209.51.161.238 > offset 358.732506 sec > > Why when it was running did it not update the clock on the server? It was working on it. You should read up on NTP a bit so you understand how it works. NTP does not "set" the clock unless you explicitly tell it to (I believe the -s switch in openntpd). Instead, it speeds up or slows down the clock to bring it into adjustment, which prevents software from seeing a sudden and space-time fabric-ripping shift in time. If you let openntpd run for a while, possibly a few hours, you'd see the time come in to sync. > From a different computer I can not get the time from the server > running openntpd. What error do you get? Run ntpdate -d on the other computer to see _why_ it's refusing to sync. I would guess it's because the OpenNTPd server knows that it's not in sync yet, and thus refuses to sync other machines. -- Bill Moran http://www.potentialtech.com