From owner-freebsd-arch@FreeBSD.ORG  Thu Jul 31 04:13:46 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4505237B401; Thu, 31 Jul 2003 04:13:46 -0700 (PDT)
Received: from critter.freebsd.dk (esplanaden.cybercity.dk [212.242.40.114])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5D69D43FA3; Thu, 31 Jul 2003 04:13:45 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h6VBDh3D002923;
	Thu, 31 Jul 2003 13:13:43 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Sean Kelly <smkelly@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 30 Jul 2003 19:23:04 CDT."
             <20030731002304.GA5131@edgemaster.zombie.org> 
Date: Thu, 31 Jul 2003 13:13:43 +0200
Message-ID: <2922.1059650023@critter.freebsd.dk>
cc: arch@freebsd.org
Subject: Re: A working watchdog API 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2003 11:13:46 -0000

In message <20030731002304.GA5131@edgemaster.zombie.org>, Sean Kelly writes:

>Comments? Ideas? Questions? Death threats?

Looks good to me.

I tacitly assume that (something like) the <sys/watchdog.h> interface
will remain for userland components to "take over" the patting of
the watchdog.

One thing we may want to consider is to write a configurable userland
watchdogd process which will examine various vital statistics and
pat the watchdog if everything is fine.

Amongst the things I could imagine watchdogd looking at:
	Precense of carrier on network interfaces
	A certain minimum amount of trafic on an interface
	Ping'ability of a given IP#
	Being able to connect to a given tcp port.
	A given process still running.
	Being able to create, write, fsync, close and remove a given file
	(to see that a disk is not hung).
etc.

Any takes ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.