Date: Fri, 4 Feb 2005 10:33:13 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Marco van Lienen <marco+freebsd-stable@lordsith.net> Cc: freebsd-stable@freebsd.org Subject: Re: Adjusting time on a secured FreeBSD machine. Message-ID: <20050204102956.W53694@carver.gumbysoft.com> In-Reply-To: <20050204161415.GA54492@lordsith.net> References: <420265D2.8050503@gopostal.ca> <200502031803.j13I3NZR016534@the-macgregors.org> <20050204161415.GA54492@lordsith.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 4 Feb 2005, 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. No; the kernel keeps the hardware clock in sync automatically. The problem is that you need to step the clock before incrementing securelevel. Once the clock is correct, you can increment securelevel with ntp running and it'll keep the clock on time. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050204102956.W53694>