From owner-freebsd-isp  Wed Mar 24  9:25: 9 1999
Delivered-To: freebsd-isp@freebsd.org
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
	by hub.freebsd.org (Postfix) with ESMTP id D960015494
	for <freebsd-isp@FreeBSD.ORG>; Wed, 24 Mar 1999 09:25:00 -0800 (PST)
	(envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id RAA51878;
	Wed, 24 Mar 1999 17:24:32 GMT
Message-ID: <36F91FB9.EA61A2D4@tdx.co.uk>
Date: Wed, 24 Mar 1999 17:24:09 +0000
From: Karl Pielorz <kpielorz@tdx.co.uk>
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Jason J. Horton" <jason@intercom.com>
Cc: freebsd-isp@FreeBSD.ORG
Subject: Re: BIND 8.2
References: <Pine.BSF.4.10.9903241128450.28439-100000@mail.intercom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

"Jason J. Horton" wrote:
> 
> Has anyone had a problem with the new version
> of bind? I have noticed that the process has
> been dying, dumping a huge core file.

I've been running it here under 4.0-current for about the past week, with
quite a few hundred domains, and no problems...
 
> What is a good way to monitor a process, and
> restart if it dies?

Probably to put a script run from the crontab that checks it say, every 5
minutes then re-run's it if it's not running...?

-Kp


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message