Date: Thu, 21 Oct 1999 15:33:19 -0400 From: James FitzGibbon <james@targetnet.com> To: FreeBSD-gnats-submit@freebsd.org Subject: docs/14449: update to init(8) manpage Message-ID: <E11eNxf-00026L-00@dev1.lab>
next in thread | raw e-mail | index | archive | help
>Number: 14449 >Category: docs >Synopsis: time clamping effect of securelevel not documented >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 21 12:40:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: James FitzGibbon >Release: FreeBSD 3.3-19991019-STABLE i386 >Organization: Targetnet.com Inc. >Environment: System running with kern.securelevel set to 3 >Description: If kern.securelevel is greater than 1, time changes are clamped in the kernel to no more than plus or minus one second at a time. This is not documented in the init(8) manpage. Running xntpd on a system not already very close to the stratum 1 clocks will fill the syslog with messages "Time adjustment clamped to +1 second". Without groping through the sys/kern/kern_time.c sourcefile, end users wouldn't know that the securelevel was at the heart of the problem. >How-To-Repeat: Confiugre a machine with a securelevel of 2 or 3 Get the date from an ntp server. Set the system clock to 5 minutes behind the ntp server. Run xntpd, specifying the same server as a upstream source of ntp data. >Fix: Document the time-clamping effects of "securelevel > 1" in the init(8) manpage. If other effects of changing securelevel are not documented, these should be added as well. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E11eNxf-00026L-00>