Date: Mon, 14 Feb 2005 10:40:55 -0600 From: Greg Barniskis <nalists@scls.lib.wi.us> To: aklist_061666 <aklist_061666@enigmedia.com>, questions@freebsd.org Subject: Re: Newbie: BIND conf "file not found" error Message-ID: <4210D497.3040200@scls.lib.wi.us> In-Reply-To: <015d01c512a5$f9d24ce0$0b01a8c0@enigmedia.net> References: <010e01c51076$41b714f0$0b01a8c0@enigmedia.net> <441xbk4hcq.fsf@be-well.ilk.org> <015d01c512a5$f9d24ce0$0b01a8c0@enigmedia.net>
next in thread | previous in thread | raw e-mail | index | archive | help
aklist_061666 wrote: > Hi Lowell: From the command line it runs fine. > > So, are you suggesting that the process doesn't have permissions to open > the file? If so, wouldn't I see a permissions error message instead of > file-not-found? > > TIA, AK > > ----- Original Message ----- From: "Lowell Gilbert" > <freebsd-questions-local@be-well.ilk.org> > To: "aklist_061666" <aklist_061666@enigmedia.com> > Sent: Sunday, February 13, 2005 10:20 AM > Subject: Re: Newbie: BIND conf "file not found" error > > >> "aklist_061666" <aklist_061666@enigmedia.com> writes: >> >>> One last question on configuring Named to run: >>> >>> I'm able to start BIND from the command line with: >>> >>> /usr/sbin/named -c /etc/named.conf >>> >>> but when I modify my rc.conf file with: >>> >>> named_enable="YES" >>> named_program="/usr/sbin/named" >>> named_flags="-u bind -c /etc/named.conf" >>> >>> I get an error on startup: >>> >>> Feb 11 14:47:53 ns2 named[275]: none:0 open: /etc/named.conf: file >>> not found >>> Feb 11 14:47:53 ns2 named[275]: loading configruation: file not found >>> Feb 11 14:47:53 ns2 named[275]: exiting (due to fatal error) >>> >>> what's wrong with my config-file path parameter in rc.conf? >> >> >> Permisssions? Try running it from the command line the same way you >> do from the startup scripts. I think your problem is related to the fact that when you run named in a sandbox, the path to /etc/named.conf becomes relative to the sandbox. So when named flags indicate /etc/named.conf, that file must actually reside at /your/chroot/path/etc/named.conf. (keep in mind that this advice is from dim memory of having this problem over a year ago, and it could be I'm just wrong, but I'm relatively sure about sandboxing having this problem ;-) -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) <gregb at scls.lib.wi.us>, (608) 266-6348
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4210D497.3040200>