Antwort: none:0: open: /chroot/named/etc/named.conf: file not found
holger.honert at signal-iduna.de
holger.honert at signal-iduna.de
Thu Mar 17 07:09:34 UTC 2005
If you are running chrooted and your named.conf is located in the chrooted
/etc -directory you con ommit the -c statement because the config file is
in the standard-directory named expects to.
Kind Regards/Freundlichen Gruß
Holger Honert
KOMN-97851
SIGNAL IDUNA Gruppe
Joseph-Scherer-Str. 3
44139 Dortmund
Phone: +49 231/135-4043
FAX: +49 231/135-2959
mailto: holger.honert at signal-iduna.de
akudesia at gmail.com (adarsh)
Gesendet von: bind-users-bounce at isc.org
16.03.2005 18:31
An: comp-protocols-dns-bind at isc.org
Kopie:
Thema: none:0: open: /chroot/named/etc/named.conf: file not found
After I chrooted my perfectly working BIND on RED HAT ES 3.x things
are not looking good. Everytime I attempt to start "named" using
following command
/usr/sbin/named -t /chroot/named/ -u casadmin -c
/chroot/named/etc/named.conf
i ge this...
Mar 16 12:02:51 DNSSERVER named[3215]: starting BIND 9.2.2 -t
/chroot/named/ -u casadmin -c /chroot/named/etc/named.conf
Mar 16 12:02:51 DNSSERVER named[3215]: using 1 CPU
Mar 16 12:02:51 DNSSERVER named[3215]: loading configuration from
'/chroot/named/etc/named.conf'
Mar 16 12:02:51 DNSSERVER named[3215]: none:0: open:
/chroot/named/etc/named.conf: file not found
Mar 16 12:02:51 DNSSERVER named[3215]: loading configuration: file not
found
Mar 16 12:02:51 DNSSERVER named[3215]: exiting (due to fatal error)
named"
I have verified the permissions as specified in
http://www.losurs.org/docs/howto/Chroot-BIND-2.html
but no help. Keep getting same error.
Any help would be appreciated to resolve this issues ASAP.
Adarsh
More information about the bind-users
mailing list