From owner-freebsd-stable@FreeBSD.ORG Fri Feb 4 18:47:18 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44D7216A4CE for ; Fri, 4 Feb 2005 18:47:18 +0000 (GMT) Received: from mailgate2.dslextreme.com (mailgate2.dslextreme.com [66.51.199.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2E8343D55 for ; Fri, 4 Feb 2005 18:47:17 +0000 (GMT) (envelope-from junk-it@dslextreme.com) Received: from mail5.dslextreme.com (unknown [192.168.7.93]) by mailgate2.dslextreme.com (Postfix) with SMTP id D733E3A63D7 for ; Fri, 4 Feb 2005 10:47:13 -0800 (PST) Received: (qmail 6503 invoked from network); 4 Feb 2005 18:47:14 -0000 Received: from unknown (HELO [192.168.212.229]) (66.159.226.55) by mail5.dslextreme.com with (RC4-MD5 encrypted) SMTP; Fri, 04 Feb 2005 10:47:14 -0800 Message-ID: <4203C330.5000702@dslextreme.com> Date: Fri, 04 Feb 2005 10:47:12 -0800 From: Stan User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marco van Lienen References: <420265D2.8050503@gopostal.ca> <200502031803.j13I3NZR016534@the-macgregors.org> <20050204161415.GA54492@lordsith.net> In-Reply-To: <20050204161415.GA54492@lordsith.net> X-DSLExtreme-MailGate-Information: Please contact the ISP for more information X-DSLExtreme-MailGate: Found to be clean X-MailScanner-From: junk-it@dslextreme.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-stable@freebsd.org Subject: Re: Adjusting time on a secured FreeBSD machine. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2005 18:47:18 -0000 I ran into this same problem. After trying various things, I finally gave up and did it the easy way. If you don't mind rebooting, the easiest thing to do is set the clock in the BIOS as accurately as possible, then let ntpd fine tune it from there. Regards, Stan Marco van Lienen wrote: >On Thu, Feb 03, 2005 at 06:03:48PM -0000, Rob MacGregor wrote: > > >>Not within NTPd itself. You could go with manually stepping the time in 1s >>intervals. It's either that or drop the securelevel in rc.conf and reboot (then >>reset the securelevel). >> >>Of course, you probably want to make sure the hardware clock has a vaguely >>accurate idea of time. That'll help in future. >> >> > >Isn't there a tool like hwclock for Linux? >With this tool you can actually set the hardware clock to the current system >time or vice versa. >Just wondering. > >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > >