Date: Mon, 17 Sep 2001 10:29:16 +1200 From: Jonathan Chen <jonathan.chen@itouch.co.nz> To: DrTebi <drtebi@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: security level and system time question Message-ID: <20010917102916.C24994@itouchnz.itouch> In-Reply-To: <001701c13efc$7b6853c0$c8e1b3d8@liquidground.com>; from drtebi@yahoo.com on Sun, Sep 16, 2001 at 03:11:05PM -0700 References: <001701c13efc$7b6853c0$c8e1b3d8@liquidground.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 16, 2001 at 03:11:05PM -0700, DrTebi wrote:
> Hello,
> I understand that it is not possible to run ntpdate or date when in security
> level 2 -- at least not when the time is off by more than one second.
> I must say that's quite impossible to have a system clock that is not
> inaccurate, at least mine are all not.
>
> What could be done to fix this? I would prefer to stay in security level 2,
> but don't want my time to be off by 1 minute every month.
> Would it make sence to run a cron job (a'la ntpdate ntp.netcom.ca) every
> minute? Does that sound unreasonable?
Use ntpd(8). Set the date once using ntpdate, then get ntpd(8) running.
You can bump up your security level at this point, as ntpd will adjust
the time while it's running.
--
Jonathan Chen <jonathan.chen@itouch.co.nz>
----------------------------------------------------------------------
"Irrationality is the square root of all evil"
- Douglas Hofstadter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010917102916.C24994>