From owner-freebsd-questions@FreeBSD.ORG  Sat Nov 20 06:46:04 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6B40B16A4CE
	for <freebsd-questions@freebsd.org>;
	Sat, 20 Nov 2004 06:46:04 +0000 (GMT)
Received: from jeremino.homeunix.net (jeremino.xs4all.nl [80.126.224.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ED98B43D55
	for <freebsd-questions@freebsd.org>;
	Sat, 20 Nov 2004 06:46:03 +0000 (GMT)
	(envelope-from kees@jeremino.hbunix.net)
Received: from jeremina.homeunix.net ([10.0.0.5])
	by jeremino.homeunix.net with smtp (Exim 4.42)
	id 1CVP0U-000108-O3
	for freebsd-questions@freebsd.org; Sat, 20 Nov 2004 07:46:02 +0100
From: Kees Plonsz <kees@jeremino.hbunix.net>
To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Date: Sat, 20 Nov 2004 07:45:56 +0100
References: <list.freebsd.questions#20041119235827.U46349@unsane.co.uk>
Lines: 15
Organization: Chaotic
User-Agent: KNode/0.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Message-Id: <20041120064603.ED98B43D55@mx1.FreeBSD.org>
Subject: Re: newsyslog and chrooted bind on 5.3
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Nov 2004 06:46:04 -0000

Vince Hoffman wrote:

> Hi all,
>  since i updated my server to 5.3 and went with the default option
> of chrooting bind, anytime named recives a HUP signal it dies. Is this
> expected ? its a bit of a bugger as i will have to use cron and a short
> shell script instead of an entry in newsyslog.conf.
> 
> Vince

There was a discussion about that a few hours ago.
Use "/etc/rc.d/named restart" instead.
I wonder if you get an error about "named/pid"
from that script if you restart named.