Your file pathnames need to be relative to the chroot.
Do you have a config file at /var/named/opt/bind/etc/named.conf?
Apparently you don't.
If you don't want to use the compiled-in pathname for /etc/named.conf,
you might want to use the -c option to specify a different
(chroot-relative) pathname.
- Kevin
Binmakhashen, Latif wrote:
> Do you guys know how to start the new version of bind in BSD with chrooted
> "-t /var/named"?
> I'm trying to make bind-9.5.0-P2 to start using the config files + the
> rndc.conf under /var/named and not from /opt/bind?
>
> # ./named -g
> 14-Aug-2008 11:52:10.971 starting BIND 9.5.0-P2 -g
> 14-Aug-2008 11:52:10.983 loading configuration from '/opt/bind/etc/named.conf'
> 14-Aug-2008 11:52:10.985 listening on IPv6 interfaces, port 53
> 14-Aug-2008 11:52:10.987 listening on IPv4 interface lo0, 127.0.0.1#53
> 14-Aug-2008 11:52:10.987 listening on IPv4 interface fxp0, 10.0.20.8#53
> 14-Aug-2008 11:52:10.988 could not configure root hints from
> 'standard/root.hint': file not found
> 14-Aug-2008 11:52:10.989 loading configuration: file not found
> 14-Aug-2008 11:52:10.990 exiting (due to fatal error)
>
> # ./named -t /var/named -g
> 14-Aug-2008 11:52:30.503 starting BIND 9.5.0-P2 -t /var/named -g
> 14-Aug-2008 11:52:30.515 loading configuration from '/opt/bind/etc/named.conf'
> 14-Aug-2008 11:52:30.516 none:0: open: /opt/bind/etc/named.conf: file not
> found
> 14-Aug-2008 11:52:30.517 loading configuration: file not found
> 14-Aug-2008 11:52:30.517 exiting (due to fatal error)
> #
>
>
> Thanks
>
>
> -- NOTICE --
> This e-mail message is confidential, intended only for the named recipient(s)
> above and may contain information that is privileged or exempt from
> disclosure under applicable law. If you have received this message in error,
> or are not the named recipient(s), please immediately notify the sender and
> delete this e-mail message from your computer.
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fr34k
> Sent: Thursday, August 14, 2008 4:37 PM
> To: [email protected]
> Subject: Re: FW: 9.5.0-P2 and socket: too many open file descriptors
>
> Hello,
> Not necessarily a requirement.
> If you are seeing "socket: too many open file descriptors" messages, then
> making the compile change for FD may be something that you want to try and
> test.
> >From what I've seen for our environment, 9.5.1b1 has been the best 9.5.x
> >version as long as it stays running :)
> For stability, we are testing hacks to 9.5.0-P2
> TIA
>
>
>
> ----- Original Message ----
> From: "Binmakhashen, Latif" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: [email protected]
> Sent: Thursday, August 14, 2008 4:13:52 PM
> Subject: RE: FW: 9.5.0-P2 and socket: too many open file descriptors
>
> I've compiled bind for HP-UX and OpenBSD 3.7.
> I've seen a lot of emails about the FD_SETSIZE?
> Does HP-UX or OpenBSD requires a compile time change to FD_SETSIZE?
>
>
> Latif
>
>
> -- NOTICE --
> This e-mail message is confidential, intended only for the named
> recipient(s) above and may contain information that is privileged or
> exempt from disclosure under applicable law. If you have received this
> message in error, or are not the named recipient(s), please immediately
> notify the sender and delete this e-mail message from your computer.
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 14, 2008 3:09 PM
> To: Binmakhashen, Latif
> Cc: [email protected]
> Subject: Re: FW: 9.5.0-P2 and socket: too many open file descriptors
>
> At Thu, 14 Aug 2008 15:01:04 -0400,
> "Binmakhashen, Latif" <[EMAIL PROTECTED]> wrote:
>
>> Is HP-UX and OpenBSD 3.7 affected by this value as well?
>>
>> I compiled them as following:
>>
>> ./configure --prefix=/opt/bind
>>
>> Please let me know as I'm concern about this.
>>
>
> I don't understand the question. What do you exactly mean by
> "affected" and "this value"? It would be helpful if you could provide
> more background details.
>
> ---
> JINMEI, Tatuya
> Internet Systems Consortium, Inc.
> -- NOTICE --
> The information transmitted is intended only for the person or
> entity to which it is addressed and may contain confidential and/or
> privileged material, the disclosure of which is governed by
> applicable law. Any review, retransmission, dissemination or other
> use of, or taking of any action in reliance upon, this information
> by persons or entities other than the intended recipient is
> prohibited. If you received this in error please contact the sender
> and destroy the materials contained in this message.
>
>
>
>
>
