freebsd stable - Jun 2004 - NTPD and SecureLevel

Hello there, every one.

I've installed and configured ntpd daemon and was wondering if it going to
work with SecureLevel higher than 1. SecureLevel 2 forbids changing the system
date and, therefore, ntpdate and rdate won't work.

How about daemonized version? Maybe it uses some other resources?

Pavel M. Rebrov

Pavel M. Rebrov wrote:
> I've installed and configured ntpd daemon and was wondering if it going
to
> work with SecureLevel higher than 1. SecureLevel 2 forbids changing the
system
> date and, therefore, ntpdate and rdate won't work.
You will want to "step" the system time at boot before the securelevel
is set.
  Afterwards, ntpd will use another mechanism to "slew" the system
time (the
adjtime() call) which ought to still be permitted by the securelevel.

-- 
-Chuck

On Jun 16, 2004, at 03:47, Pavel M. Rebrov wrote:
> I've installed and configured ntpd daemon and was wondering if it 
> going to work with SecureLevel higher than 1. SecureLevel 2 forbids 
> changing the system date and, therefore, ntpdate and rdate won't work.
Have ntpdate run before hand to get the time with in a close amount of 
the 'real' time. There should be an rc.conf item for ntpdate.

ntpd(8) doesn't actually change the time by making it 'jump' to the 
correct time; it slows down or speeds up the rate at which the timer 
runs at.

So if your system time is ahead of the 'real' time, ntpd will slow down 
the rate at which time passes ('one second' on the system clock will 
actually take longer than a 'real' second to pass). Similarly if your 
system time is behind the 'real' time ntpd will adjust the rate so that 
timer will run faster than 'real' time.

This way there are no 'jumps' in time: it is continuous.