Date: Thu, 31 Jul 2003 13:13:43 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Sean Kelly <smkelly@freebsd.org> Cc: arch@freebsd.org Subject: Re: A working watchdog API Message-ID: <2922.1059650023@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 30 Jul 2003 19:23:04 CDT." <20030731002304.GA5131@edgemaster.zombie.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2922.1059650023>