Chris Kuethe wrote:
> Why?
>
> a bit of RTFM on the named manpage suggests a way to do this.
The man page is wrong. It says:
When invoked without arguments, named will fork into two
processes for privilege separation. chroot() to
/var/named, read the default configuration file
/var/named/etc/named.conf, read any initial data, and lis-
ten for queries.
But it took me a good hour after I posted my question, after already
trying for 2 hours, to figure out that what it really means is:
When invoked without the "-t" argument...
So I have it basically working by using "-t /". But if there's a better
way I'd love to know about it.
> But again, why?
Because my configuration files, named.conf and all the zone files, must
be at /export/config/named/... And there's no way, other than removing
the chroot AFAIK, to get named to read the configuration from where I
have the files. And you'll ask why don't I just put the files in
/var/named/etc? Because those files are version control managed, backup
managed, and RAID managed. Or more precisely my entire /export is highly
controlled to have fault tolerance, backups, complete file histories,
and access controls.
Rene Rivera wrote:
Or alternatively, to have the configuration files read from someplace
else. I.e. having the named.conf someplace other than /var/named/etc.
And have the conf be able to have:
options {
pid-file "/var/run/named.pid";
directory "/export/config/named";
...
For example.
--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
