Date: Thu, 19 Aug 1999 16:30:47 -0600 (MDT)
From: "David G. Andersen" <danderse@cs.utah.edu>
To: Brett Glass <brett@lariat.org>
Cc: Archie Cobbs <archie@whistle.com>, Goran.Lowkrantz@infologigruppen.se (Lowkrantz Goran), freebsd-security@FreeBSD.ORG ('freebsd-security@FreeBSD.ORG')
Subject: Re: Securelevel 3 ant setting time
Message-ID: <14268.33906.359749.40458@torrey.cs.utah.edu>
In-Reply-To: Brett Glass's message of Thu, August 19 1999 <4.2.0.58.19990819161554.04790800@localhost>
References: <B500F74C6527D311B61F0000C0DF5ADC07ECB5@valhall.ign.se> <199908191819.LAA94866@bubba.whistle.com> <4.2.0.58.19990819161554.04790800@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
"Maybe". (Probably?)
When ntpdate sees a small time delta (less than 1/2 second off), it
will use the adjtime() call to slew the clock time, which is
permitted. However, if the delta is large for some reason, then it
will go in and use the sledgehammer approach - settimeofday().
>From the ntpdate manpage:
The latter technique is less disruptive and
more accurate when the offset is small, and works quite well when ntpdate
is run by cron(8) every hour or two.
So, you'll probably be OK doing it that way, *but* if you get too far
off during the time period, then you won't be able to correct for it.
-Dave
Lo and Behold, Brett Glass said:
> My server uses a cron job and ntpupdate to grab tne time from the
> best of several accurate government servers. Would securelevel 3 allow
> this?
--
work: danderse@cs.utah.edu me: angio@pobox.com
University of Utah CS Department http://www.angio.net/
"If you haul a geek up a crack, you will bloody their fingers for a day...
If you teach a geek to climb, you will bloody their fingers for life."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14268.33906.359749.40458>