Hi John,
Perhaps you could try to chown directory /var/named to named
drwxrwx--- 3 named named
Edwin Lee
- Original Message -
From: jo...@primebuchholz.com
To: bind-users@lists.isc.org
Sent: Wednesday, August 28, 2013 2:38:11 AM
Subject: chroot /var/run permissions
Greetings,
I'm
Hello John,
jo...@primebuchholz.com writes:
What I am I missing here? /var/named/var/run and
/var/named/var/run/named
have group write permissions, so it seems it *shouldn't* be
complaining,
and the resulting files should've been owned by named, shouldn't they?
If you are running
Greetings,
I'm upgrading my bind installation on one of my hosts, and everything
seems to be working properly although I'm getting a permissions
error/warning in the log on startup:
Aug 27 14:24:45 flotsam named[13746]: Required root permissions to open
'/var/run/named.pid'.
Aug 27 14:24:45
/var/run/named.pid and /var/run/named/session.key need to be writable
by named. Additionally their parent directories need to be writable
by named so the files can be removed on shutdown. The files are
not writable by named.
-rw-r--r-- 1 root named6 Aug 27 14:35 named.pid
John,
You should see if your full root on the box what permissions named
has as a group and what the (bind/named) user has. If your running some
restricting permissions via the sudoers you may need to lighten up to 775
from the chroot'd directory down giving the ownership the named group
5 matches
Mail list logo
