From owner-freebsd-current@FreeBSD.ORG  Tue Dec 17 22:03:45 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E1D608E3;
 Tue, 17 Dec 2013 22:03:45 +0000 (UTC)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com
 [IPv6:2a00:1450:400c:c03::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 55E5A1184;
 Tue, 17 Dec 2013 22:03:45 +0000 (UTC)
Received: by mail-we0-f178.google.com with SMTP id u57so6783266wes.9
 for <multiple recipients>; Tue, 17 Dec 2013 14:03:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=qVSTFNypZq6WeErBdfAafRqrroZORN7l3uHOgaq+xcQ=;
 b=Oya8868J0kNDW4ayEPg4zm7WQyYkIDUfIRTjbHEIMP08YDHYPvzLbZJB/whLD2n/2l
 8iVwgDu1iRNc+70L+9uXwhVnIwFuF1HaX9Ok6hSVdH5fVrPoJu1n1gVkg9roZpOElfy2
 D3LFu997UXtxhZeoBf9N5E4QZIZ2gnrITr11f0oMY/7HnvrXhsqvLAj1wcJg9ulgbyVr
 7hKGi7HXtU6RiKFg7Lw5H5iUoQAYadRHObpuBUKXw9MPaY4K01iQFMuP8YTOk302VXIg
 6xtgexDS12nBW7sc7IGXA7MfY/vF4EjyKTK2X0sb7dSZO8TwGCgDaJvkx59yCt1feMwv
 22KA==
MIME-Version: 1.0
X-Received: by 10.180.95.162 with SMTP id dl2mr5182074wib.17.1387317823764;
 Tue, 17 Dec 2013 14:03:43 -0800 (PST)
Received: by 10.227.63.136 with HTTP; Tue, 17 Dec 2013 14:03:43 -0800 (PST)
In-Reply-To: <20131217232838.c4584918.ray@freebsd.org>
References: <CAFPOs6oyAs+DvcrNM8GnWNrzEVpkkNBTrHWzb-OSO90MefnB9Q@mail.gmail.com>
 <20131217232838.c4584918.ray@freebsd.org>
Date: Tue, 17 Dec 2013 14:03:43 -0800
Message-ID: <CAFPOs6qYanSOWqZmFzEB5t5JFmzKRweGkVwFapyj3piVN1j8fg@mail.gmail.com>
Subject: Re: [rfc] [patch] do not stop watchdog on shutdown
From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com>
To: Aleksandr Rybalko <ray@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "current@freebsd.org" <current@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: Tue, 17 Dec 2013 22:03:46 -0000

Hello Aleksandr

>> would anyone object to this patch?
>
> It is good idea, but sometimes shutdown sequence longer than some H/W
> watchdogs even support.
> I have one board which can do only 20sec maximum time.

yes. its up to the user to configure appropriate watchdog timeout.
this features is mostly for "light-out" type of environments where
remote hands are not easily available.

thanks
max

>> Index: src/etc/rc.d/watchdogd
>> ===================================================================
>> --- src/etc/rc.d/watchdogd      (revision 2999)
>> +++ src/etc/rc.d/watchdogd      (working copy)
>> @@ -39,4 +39,7 @@
>>  pidfile="/var/run/${name}.pid"
>>
>>  load_rc_config $name
>> +
>> +sig_stop="${watchdogd_sig_stop:-TERM}"
>> +
>>  run_rc_command "$1"
>> _______________________________________________