On Mon, 15 Nov 2004, Samuel Trommel wrote:
Recently I upgraded from 5.2.1-release to 5.3-release. When I try to
start named I get a weird error:
Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t
/var/named/etc/namedb/ -c /etc/named.conf
Nov 15 19:23:12 freebsd
El Lunes, 15 de Noviembre de 2004 19:51, Samuel Trommel escribió:
Hello,
Recently I upgraded from 5.2.1-release to 5.3-release. When I try to
start named I get a weird error:
Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind
-t /var/named/etc/namedb/ -c /etc/named.conf
I already found out (Chroot problem /dev/random /dev/null)
Thanks anyway for the help..
Samuel
-Original Message-
From: Jose M Rodriguez [mailto:[EMAIL PROTECTED]
Sent: dinsdag 16 november 2004 23:43
To: [EMAIL PROTECTED]
Cc: Samuel Trommel
Subject: Re: Named 9.3.0 weird error
,
Samuel Trommel
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Doug Barton
Sent: dinsdag 16 november 2004 3:29
To: Samuel Trommel
Cc: [EMAIL PROTECTED]
Subject: Re: Named 9.3.0 weird error at bootup
On Mon, 15 Nov 2004, Samuel Trommel wrote:
Hello
Hello,
Recently I upgraded from 5.2.1-release to 5.3-release. When I try to start
named I get a weird error:
Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t
/var/named/etc/namedb/ -c /etc/named.conf
Nov 15 19:23:12 freebsd named[1152]: command channel listening on
On Mon, 15 Nov 2004, Samuel Trommel wrote:
Hello,
Recently I upgraded from 5.2.1-release to 5.3-release. When I try to start
named I get a weird error:
Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t
/var/named/etc/namedb/ -c /etc/named.conf
I'm assuming from these command
