Date: Wed, 7 Apr 1999 17:51:04 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> 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 Message-ID: <199904080051.RAA17508@salsa.gv.tsc.tdk.com> In-Reply-To: Greg Lehey <grog@lemis.com> "Re: cvs commit: src/sys/kern kern_time.c" (Apr 8, 10:07am)
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904080051.RAA17508>