chris...@zoulas.com (Christos Zoulas) writes:
> And I don't really see the need to make the whole namedb directory owned
> by named. Even the pri directory does not need to be writable by named.
The only time named really needs to write to the config dir is for
dynamic update. The only other time
On Apr 25, 1:31am, m...@eterna.com.au (matthew green) wrote:
-- Subject: re: CVS commit: src/external/bsd/bind/dist/bin/named
|Perhaps you are confusing this directory with /var/chroot/named/etc/namedb?
|
| i'm saying that named should be configured to have this dir as
| the cwd and
In article <22061.1240544...@splode.eterna.com.au>,
matthew green wrote:
>
> Modified Files:
>src/external/bsd/bind/dist/bin/named: server.c
>
> Log Message:
> Don't log if "." is not writable. In the chrooted environment this is
> "/var/chroot/named"
In article <22061.1240544...@splode.eterna.com.au>,
matthew green wrote:
>
> Modified Files:
> src/external/bsd/bind/dist/bin/named: server.c
>
> Log Message:
> Don't log if "." is not writable. In the chrooted environment this is
> "/var/chroot/named", and there is no reason
Modified Files:
src/external/bsd/bind/dist/bin/named: server.c
Log Message:
Don't log if "." is not writable. In the chrooted environment this is
"/var/chroot/named", and there is no reason whatsoever for this to be
writable!
this seems bogus to me.
this check seem
