From owner-freebsd-current@FreeBSD.ORG  Wed Dec  4 13:42:25 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id ADA8A5EB
 for <freebsd-current@freebsd.org>; Wed,  4 Dec 2013 13:42:25 +0000 (UTC)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7F29F117B
 for <freebsd-current@freebsd.org>; Wed,  4 Dec 2013 13:42:25 +0000 (UTC)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 2D34F21495
 for <freebsd-current@freebsd.org>; Wed,  4 Dec 2013 08:42:24 -0500 (EST)
Received: from web3 ([10.202.2.213])
 by compute1.internal (MEProxy); Wed, 04 Dec 2013 08:42:24 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:subject:date:in-reply-to
 :references; s=smtpout; bh=imLDJIU/diEkSGxS30UdSyFHMAE=; b=W/BXp
 unPH6Qage9N6CwjjLBcnys2Wcr0T6g06pj/aodnANkpRsAMPfXmmtwrPXNE1sFSB
 /qcQupf02/IJpHqNfRLvxn1ok+iwpR7b18NrBKQYloJ0pUCC8WCSg6yYHxCjDWzE
 o57BZJ90/6uvRTMHucOS42fqDlew3J7+0y7l6o=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id 1103E104491; Wed,  4 Dec 2013 08:42:24 -0500 (EST)
Message-Id: <1386164544.25171.55411873.4F5A7BD4@webmail.messagingengine.com>
X-Sasl-Enc: jLpvlaWzHwVbZYxB6sEsJSj+sueB2PuicdKJ7zAf9vaD 1386164544
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-c99dcdd8
Subject: Re: making PANIC_REBOOT_WAIT_TIME a tunable
Date: Wed, 04 Dec 2013 07:42:24 -0600
In-Reply-To: <529C4446.6020508@freebsd.org>
References: <529C4446.6020508@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 13:42:25 -0000



On Mon, Dec 2, 2013, at 2:26, Colin Percival wrote:
> Hi all,
> 
> It seems that PANIC_REBOOT_WAIT_TIME has been a compile-time setting
> forever;
> and I can't see any reason for this, but I assume there was one... at
> some
> point in the distant past.
> 
> The attached patch makes it a loader tunable and sysctl.  My reason for
> wanting
> this is to make EC2 images reboot faster after a panic (not that it
> happens
> very often, of course) -- there's no point waiting for a key press at the
> console because the EC2 console is output-only.
> 
> Any objections?
> 

I tend to cheat this problem by using watchdog on my hardware servers.
This sounds quite convenient as I can't use watchdog in VMs...