Date: Thu, 16 Sep 1999 08:53:08 -0600 From: Warner Losh <imp@village.org> To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> Cc: hackers@FreeBSD.ORG, sos@FreeBSD.ORG, bde@FreeBSD.ORG Subject: Re: panic() the system from the console (was: Re: kern/13721: There is no way to force system panic from console) Message-ID: <199909161453.IAA21647@harmony.village.org> In-Reply-To: Your message of "Thu, 16 Sep 1999 18:48:13 %2B0900." <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp> References: <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp> Kazutaka YOKOTA writes:
: case _PANIC_KEY_
: #if !defined(SC_DISABLE_REBOOT) && !defined(SC_DISABLE_PANIC)
: if (securelevel <= 0)
: panic();
: #endif
: break;
:
: Any opinions?
I can see this being useful only for systems that have a problem
coming up. Otherwise, adding options SC_DISABLE_{PANIC,REBOOT} would
accomplish this as well. So I'm mildly opposed to this since it hangs
yet another thing on securelevel...
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909161453.IAA21647>