Erik Norgaard wrote:
> Mystery deepens...?
Problem solved, yet mystery deepens as to why this happened:
I first tried to reinstall bind9 to check that some file had not been
messed up by installation of something else. Didn't change a thing.
Then I moved my old chroot dir and created a new one
Nelis Lamprecht wrote:
> Oops my bad. The only other explanation I can think of then is that
> the path for the pid file may be specified incorrectly in your
> named.conf in relation to your chroot ?
I thought that too. First, I had no path specified in named.conf,
defaults to /var/run/named.pid
On Wed, 10 Nov 2004 13:29:23 +0100, Erik Norgaard <[EMAIL PROTECTED]> wrote:
> Nelis Lamprecht wrote:
>
> > Shouldn't you be using the command named -g bind -u bind -t /var/named
> > ?
>
> No, that's bind8. On bind9 '-u bind' sets user _and_ group. -g is
> foreground to catch the output.
>
Nelis Lamprecht wrote:
> Shouldn't you be using the command named -g bind -u bind -t /var/named ?
No, that's bind8. On bind9 '-u bind' sets user _and_ group. -g is
foreground to catch the output.
Erik
--
Ph: +34.666334818 web: www.locolomo.org
S/MIME Certi
On Wed, 10 Nov 2004 12:29:59 +0100, Erik Norgaard <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I had a working BIND9 running but needed to restart after updating the
> zone file with the following command:
>
> # /usr/local/sbin/named -g -u bind -t /var/named -c /etc/named.conf
>
> But this failed:
>
S
Hi,
I had a working BIND9 running but needed to restart after updating the
zone file with the following command:
# /usr/local/sbin/named -g -u bind -t /var/named -c /etc/named.conf
But this failed:
Nov 10 12:23:58.110 starting BIND 9.2.3 -g -u bind -t /var/named -c
/etc/named.conf
Nov 10 12:23:
