From owner-cvs-all  Wed Apr  7 17:53:16 1999
Delivered-To: cvs-all@freebsd.org
Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 94376158FD; Wed,  7 Apr 1999 17:53:13 -0700 (PDT)
	(envelope-from gdonl@tsc.tdk.com)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
	by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id RAA05236;
	Wed, 7 Apr 1999 17:51:06 -0700 (PDT)
	(envelope-from gdonl@tsc.tdk.com)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
	by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id RAA18791;
	Wed, 7 Apr 1999 17:51:05 -0700 (PDT)
Received: (from gdonl@localhost)
	by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA17508;
	Wed, 7 Apr 1999 17:51:04 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199904080051.RAA17508@salsa.gv.tsc.tdk.com>
Date: Wed, 7 Apr 1999 17:51:04 -0700
In-Reply-To: Greg Lehey <grog@lemis.com>
       "Re: cvs commit: src/sys/kern kern_time.c" (Apr  8, 10:07am)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Greg Lehey <grog@lemis.com>, Nick Sayer <nsayer@FreeBSD.org>,
	cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/sys/kern kern_time.c
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

On Apr 8, 10:07am, Greg Lehey wrote:
} Subject: Re: cvs commit: src/sys/kern kern_time.c
} On Wednesday,  7 April 1999 at  9:36:57 -0700, Nick Sayer wrote:
} > nsayer      1999/04/07 09:36:57 PDT
} >
} >   Modified files:
} >     sys/kern             kern_time.c
} >   Log:
} >   If securelevel>1, allow the clock to be adjusted negatively only up to
} >   1 second prior to the highest the clock has run so far. This allows
} >   time adjusters like xntpd to do their work, but the worst a miscreant
} >   can do is "freeze" the clock, not go back in time.
} 
} Does this mean that if somebody accidentally sets the time to the
} wrong year, the only thing he can do to fix it is to reboot in
} single-user mode?

If they are running with securelevel > 1, they won't be able to set the
time to the wrong year with this change (and the followup change that
prevents the clock from being set too far into the future).

} What do
} people doing Y2K tests do?

Hopefully they change the time in single user mode.  Otherwise they
might cause cron to decide that it needs to run all the cron jobs
hundreds of times in order to catch up ;-)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message