Date: Fri, 8 May 2009 11:49:27 -0500 From: Dan Corrigan <dancorrigan1@gmail.com> To: freebsd-bugs@freebsd.org Subject: possible bug with base install of bind on Freebsd 7.2-RELEASe Message-ID: <291ddc4f0905080949l64e8271fkee90f70cbe099926@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?291ddc4f0905080949l64e8271fkee90f70cbe099926>