From owner-freebsd-current Wed Aug 1 0:32:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 0EDD437B406; Wed, 1 Aug 2001 00:32:17 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15RqV6-000OpP-00; Wed, 01 Aug 2001 09:33:04 +0200 From: Sheldon Hearn To: Vincent Poy Cc: John Baldwin , Kris Kennaway , current@FreeBSD.org Subject: Re: -current lockups In-reply-to: Your message of "Tue, 31 Jul 2001 12:06:49 -1000." <20010731120618.A87252-100000@oahu.WURLDLINK.NET> Date: Wed, 01 Aug 2001 09:33:03 +0200 Message-ID: <95442.996651183@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 31 Jul 2001 12:06:49 -1000, Vincent Poy wrote: > Yeah, that's the weird part... I thought adding a DDB_UNATTENDED > as a option would atleast make it reboot or something... For the record, DDB_UNATTENDED is mostly pointless. It just sets the default value of debug.debugger_on_panic, which you can just as well set in /etc/sysctl.conf. Unless, of course, you're seeing a panic in the startup process. But then do you really want an indefinite panic cycle? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message