From owner-freebsd-bugs  Wed Nov 26 10:16:41 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA06495
          for bugs-outgoing; Wed, 26 Nov 1997 10:16:41 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA06490
          for <bugs@FreeBSD.ORG>; Wed, 26 Nov 1997 10:16:37 -0800 (PST)
          (envelope-from jin@george.lbl.gov)
Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id KAA08150 for bugs@FreeBSD.ORG; Wed, 26 Nov 1997 10:16:28 -0800
Date: Wed, 26 Nov 1997 10:16:28 -0800
From: "Jin Guojun[ITG]" <jin@george.lbl.gov>
Message-Id: <199711261816.KAA08150@george.lbl.gov>
To: bugs@FreeBSD.ORG
Subject: kern.securelevel auto from 0 to 1 ?bug/feature?
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I do not remember if this is true before 2.1.7.  Looks like that this
happens in all current versions.
I try to set kernel.securelevel=0 at the last line in rc or rc.local,
when the machine boot, it always reset the level to 1 before given the
LOGIN prompt. This causes X server will not start due to the KDENBAIO failed
(Operation not permitted). I have asked XFree86 folks and they seems not able
to resolve this issue.
A hint, if kernel.securelevel is set to 0 after login as root rather than
set in booting time, it will stay. It is apperently triggered by some booting
process.
So, I wonder if something can be fixed in FreeBSD kernel to prevent this
automatically securelevel jumping?

Thanks,

	-Jin