Date: Sun, 3 Aug 2008 22:47:19 +0800 From: Eugene Grosbein <eugen@kuzbass.ru> To: Ian Smith <smithi@nimnet.asn.au> Cc: net@freebsd.org Subject: Re: permissions on /etc/namedb Message-ID: <20080803144719.GA33577@svzserv.kemerovo.su> In-Reply-To: <Pine.BSF.3.96.1080803210452.13190B-100000@gaia.nimnet.asn.au> References: <20080803073803.GA10321@grosbein.pp.ru> <Pine.BSF.3.96.1080803210452.13190B-100000@gaia.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 03, 2008 at 10:32:22PM +1000, Ian Smith wrote: > > I need /etc/namedb to be owned by root:bind and have permissions 01775, > > so bind may write to it but may not overwrite files that belong to root > > here, and I made it so. Suprise! > > > > # /etc/rc.d/named restart > > Stopping named. > > Waiting for PIDS: 1892. > > etc/namedb changed > > gid expected 0 found 53 modified > > permissions expected 0755 found 01775 modified > > Starting named. > > Are you running /etc/namedb linked to chroot'd /var/named/etc/namedb? > If so, that'd be mtree restoring perms from /etc/mtree/BIND.chroot.dist I just have 'named_enable="YES"' in /etc/rc.conf, it's 6.3-STABLE and stock bind9. I could set named_chroot_autoupdate="NO", but I see now it won't mount devfs into chroot are in that case. Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080803144719.GA33577>