From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 5 18:40:41 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 486371065675 for ; Sun, 5 Apr 2009 18:40:41 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id EEB548FC15 for ; Sun, 5 Apr 2009 18:40:40 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (pD954FF67.dip.t-dialin.net [217.84.255.103]) by redbull.bpaserver.net (Postfix) with ESMTP id 7C7222E051; Sun, 5 Apr 2009 20:40:35 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.2.103]) by outgoing.leidinger.net (Postfix) with ESMTP id B0F4210C653; Sun, 5 Apr 2009 20:40:30 +0200 (CEST) Date: Sun, 5 Apr 2009 20:40:28 +0200 From: Alexander Leidinger To: Doug Ambrisko Message-ID: <20090405204028.0000654f@unknown> In-Reply-To: <200904031419.n33EJYb8069855@ambrisko.com> References: <20090403084601.108111xg6o3b49ms@webmail.leidinger.net> <200904031419.n33EJYb8069855@ambrisko.com> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.10.13; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 7C7222E051.274A6 X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-14.2, required 6, BAYES_00 -15.00, J_CHICKENPOX_21 0.60, J_CHICKENPOX_22 0.60, RDNS_DYNAMIC 0.10, SMILEY -0.50) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Sun, 05 Apr 2009 18:44:14 +0000 Cc: freebsd-hackers@freebsd.org, Andriy Gapon Subject: Re: watchdog: hw+sw? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Apr 2009 18:40:42 -0000 On Fri, 3 Apr 2009 07:19:34 -0700 (PDT) Doug Ambrisko wrote: > We start watchdogd manually with our own rc.d script mainly since > I noticed Dell pe2650's do false triggers :-( Also I wanted to check > that our app. is functioning so we'd need to start after that. It > would be good to add flags option to the stock start-up scripts. > Just having watchdogd running without checking on anything real tends > to be useless since it is usually swapped in and can run just fine > without depending on much of the system. In the mean time I noticed that the watchdogd can be started with flags just by adding watchdogd_flags="..." to rc.conf. So I just needed to write a shell script which checks the disks which cause problems sometimes, and add a line to rc.conf and now I'm satisfied (... but this should be documented somewhere more obvious). For your app watching stuff, why not write a shell script which checks for a file in a mfs which the app-start creates (if the file is there and the pid not, the app died), and let the WD run this script. This way you can use the default start script. Bye, Alexander.