From owner-freebsd-questions@FreeBSD.ORG Thu Nov 11 09:33:00 2004 Return-Path: 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 31CFD16A4CE for ; Thu, 11 Nov 2004 09:33:00 +0000 (GMT) Received: from top.daemonsecurity.com (FW-182-254.go.retevision.es [62.174.254.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E67743D5F for ; Thu, 11 Nov 2004 09:32:59 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from [192.168.0.32] (charm.daemonsecurity.com [192.168.0.32]) by top.daemonsecurity.com (Postfix) with ESMTP id 67B6EA1426; Thu, 11 Nov 2004 10:30:28 +0100 (CET) Message-ID: <419331C4.4000000@locolomo.org> Date: Thu, 11 Nov 2004 10:32:52 +0100 From: Erik Norgaard Organization: Loco Lomography User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040918 X-Accept-Language: en, en-us, da, it, es MIME-Version: 1.0 To: Gerard Samuel References: <4192375E.7050603@trini0.org> <4192C57E.8080804@trini0.org> In-Reply-To: <4192C57E.8080804@trini0.org> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsdquestions Subject: Re: BIND9 dump file X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 09:33:00 -0000 Gerard Samuel wrote: >> Im getting a bunch of these in the logs -> >> Nov 10 10:30:48 gatekeeper named[312]: dumping master file: >> master/tmp-SLtSQEmBBK: open: permission denied >> >> So I figured a filesystem permissions problem. I chowned >> Thanks for any info that you may provide... > Im confused. I've read the named and rc.conf man pages, and didn't find > out > why named is behaving as it is. I don't know if this will help or is related. I had a problem with named not creating the pid-file with a permision denied error (see other thread). I eventually solved it by creating a new chroot-dir and setting permissions on that. It still remains a mystery to me why I ever got that problem or why this worked. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2