From owner-freebsd-questions Tue Jan 15 2:50:24 2002 Delivered-To: freebsd-questions@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id B38EA37B41A for ; Tue, 15 Jan 2002 02:50:21 -0800 (PST) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Tue, 15 Jan 2002 10:50:08 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 16QRA0-00034k-00; Tue, 15 Jan 2002 10:49:44 +0000 Date: Tue, 15 Jan 2002 10:49:44 +0000 (GMT) From: Jan Grant X-X-Sender: To: MurrayTaylor Cc: Chris Dillon , Joe & Fhe Barbish , FBSD Questions Subject: Re: ntpd as time server? In-Reply-To: <000501c19d5c$0a4dafa0$022aa8c0@homenet.xxx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 15 Jan 2002, MurrayTaylor wrote: > Akk.. and the one other bit of magic that makes it work > Xntpd and ntpdate want to use the same port 123, which gets them knotted.. > So the entry in crontab is NOT just > > ntpdate aaa.bbb.ccc.ddd > > but instead is > > /root/bin/ntpcron > > which is a script as follows > > #!/bin/sh > kill `cat /var/run/xntpd.pid` > sleep 1 > ntpdate aaa.bbb.ccc.ddd > sleep 1 > xntpd -p /var/ruun/xntpd.oid > > > Ie drop off the xntdp daemon while we tweek the systems clock Rather than step your clock, why not just teach ntpd about the time server it should synchronise to? It's pretty configurable, and you'll get smooth time changes if you do this. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk It's a sad fact that the word "semantics" seems to have lost all meaning. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message