From owner-freebsd-current@FreeBSD.ORG Mon Sep 19 12:49:19 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82500106566B for ; Mon, 19 Sep 2011 12:49:19 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CFA178FC0A for ; Mon, 19 Sep 2011 12:49:18 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA11219; Mon, 19 Sep 2011 15:49:13 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E773A49.20300@FreeBSD.org> Date: Mon, 19 Sep 2011 15:49:13 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.2) Gecko/20110907 Thunderbird/6.0.2 MIME-Version: 1.0 To: Arnaud Lacombe References: <58772.1316203388@critter.freebsd.dk> In-Reply-To: X-Enigmail-Version: undefined Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Poul-Henning Kamp , FreeBSD-Current Subject: Re: Very imprecise watchdogd(8) timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 12:49:19 -0000 on 16/09/2011 23:59 Arnaud Lacombe said the following: > in which case the current notifier-based architecture is broken. You > may want to have a soft-watchdog triggering after 5s, and a fallback > hardware watchdog triggering after 60s. So let's start with the real problem, FreeBSD watchdog infrastructure doesn't expose an API to do what you described above. I think that it would be a rather small part to change the representation of timeouts from current form to, say, value + unit encoding. -- Andriy Gapon