From owner-freebsd-bugs@FreeBSD.ORG  Fri May  8 17:18:48 2009
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 047F8106566C
	for <freebsd-bugs@freebsd.org>; Fri,  8 May 2009 17:18:48 +0000 (UTC)
	(envelope-from phisher1@gmail.com)
Received: from mail-ew0-f159.google.com (mail-ew0-f159.google.com
	[209.85.219.159])
	by mx1.freebsd.org (Postfix) with ESMTP id 851468FC15
	for <freebsd-bugs@freebsd.org>; Fri,  8 May 2009 17:18:47 +0000 (UTC)
	(envelope-from phisher1@gmail.com)
Received: by ewy3 with SMTP id 3so1971954ewy.43
	for <freebsd-bugs@freebsd.org>; Fri, 08 May 2009 10:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:sender:received:date
	:x-google-sender-auth:message-id:subject:from:to:content-type;
	bh=X+mGIfML7gbM3uQ4MffM5/jJ+AsVn4I22nxI9v9CR7Y=;
	b=iHo82LCWBP0HXGghyRjTzyPrlSVCmtoQe+50bHHjbhwMJ0Y1NyfzJdFnC+eWi6W67L
	uWJGpz96/y4k+2ZD6lwaxl/FNvYJ/potZPwnCs7Y4gri+ol04actU//Kr2QUIdEuw8/y
	BtHx2tlopkQTlAw/MgMeT+2n9/J6RYJu7zET8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:sender:date:x-google-sender-auth:message-id:subject
	:from:to:content-type;
	b=xdK0FW5euCUqR5/p9RwdHx8eBHO8ZDOFLX05mux9hw7SBQITEAXdGe9Jp1v+V1jYAa
	5oamEqrzgLOiSk1gQyNiBuS3pyPARILjPwk7hhViOyp/8mS0OqO54lGKGeFirx2Nj01k
	vTMENv7DeoQtHdf1dpuyy4TvtD41OM6iMxbdY=
MIME-Version: 1.0
Sender: phisher1@gmail.com
Received: by 10.210.12.18 with SMTP id 18mr995165ebl.13.1241801367644; Fri, 08 
	May 2009 09:49:27 -0700 (PDT)
Date: Fri, 8 May 2009 11:49:27 -0500
X-Google-Sender-Auth: 6a283869cc92ae3f
Message-ID: <291ddc4f0905080949l64e8271fkee90f70cbe099926@mail.gmail.com>
From: Dan Corrigan <dancorrigan1@gmail.com>
To: freebsd-bugs@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: possible bug with base install of bind on Freebsd 7.2-RELEASe
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 May 2009 17:18:48 -0000

On one of my semi-production nameservers I just upgraded from 7.1-RELEASE-p4
to 7.2-RELEASE, I started noticing log entries in /var/log/messages

May  8 11:26:06 phishbox named[32909]: the working directory is not writable

I thought this may have been caused my some paranoid permission I set on the
machine.
After troubleshooting for a while, I tested on a test machine at work, whose
only task is to run a daily rsync to back up another machine.

This test machine was also upgraded from 7.1-RELEASE-p4 to 7.2-RELEASE.
Nothing has been touched in /etc/namedb  All I did was add the entry into
/etc/rc.conf to enable named, named_enable="YES"

I tried to start named and got the same error:
May  8 11:44:42 danfreebsd named[1090]: the working directory is not
writable

I would gladly paste the config from either machine, but other than adding
one user and adding a cronjob to rsync, the test machine is completely
default.

I tried searching the freebsd bugs archive list to see if this bug has
already been discussed, but I couldn't find it.
If this is the incorrect place to report this, I apologize.

Thanks,
Dan