Date: Sun, 17 May 2009 14:56:25 GMT From: Wouter Snels <nospam@ofloo.net> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/134616: named[32238]: the working directory is not writable Message-ID: <200905171456.n4HEuPi7082244@www.freebsd.org> Resent-Message-ID: <200905171500.n4HF06HK002051@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 134616 >Category: misc >Synopsis: named[32238]: the working directory is not writable >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun May 17 15:00:06 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Wouter Snels >Release: FreeBSD 7.2 amd64 >Organization: >Environment: FreeBSD narf.ofloo.net 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 15 22:55:39 CEST 2009 ofloo@narf.ofloo.net:/usr/obj/usr/src/sys/OFL amd64 >Description: When restarting i always get this error in my log that the working directory of named wasn't writable, .. so i chown the /var/named directory to bind, .. but i noticed that after restarting the daemon that the permissions where set back to what they where. instead of making such fixes: directory "/etc/namedb/letskeepthisdirwriteable"; it might be more reasonable to change, BIND.chroot.dist to use bind instead of root user. >How-To-Repeat: restart the bind daemon >Fix: # $FreeBSD: src/etc/mtree/BIND.chroot.dist,v 1.6.20.1 2009/04/15 03:14:26 kensmith Exp $ # # Please see the file src/etc/mtree/README before making changes to this file. # /set type=dir uname=root gname=wheel mode=0755 << change uname=bind >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905171456.n4HEuPi7082244>