none:0: open: /chroot/named/etc/named.conf: file not found

[Kevin Darcy]

The -t and -c arguments are additive, I believe, so this is what you'd 
expect to get if there is no file at 
/chroot/named/chroot/named/etc/named.conf.

If your config file is, instead, at /chroot/named/etc/named.conf, then 
you shouldn't even need the -c argument.

                                                                         
                                       - Kevin

adarsh wrote:

>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
>
>
>
>
>
>  
>