Am Mi, den 21.04.2004 schrieb david um 07:17:
> If you include bind-chroot in your system (not sure what "include" means,
> help needed), then the NAMED service automatically prefixes
> /var/named/chroot/ in front of path names. This means that what you
"include" means installation of the RPM called bind-chroot-9.2.2.P3-9.
Its content is:
/var/named/chroot/dev/null
/var/named/chroot/dev/random
/var/named/chroot/etc/named.conf
/var/named/chroot/etc/rndc.key
/var/named/chroot/var/named
/var/named/chroot/var/run/named
/var/named/chroot/var/tmp
> thought of as /etc/named.conf becomes /var/named/chroot/etc/named.conf. In
> your "named.conf" file, if you specify a directory for your zone files,
> this same prefixing occurs.
No, the chroot environment path does not appear anywhere in the config
files for the chrooted bind! That should be logical. The chroot ==
changed root is for the application transparent. That is what you can
think of the inner meaning or purpose of chrooting. So in named.conf you
i.e. find as path:
options {
directory "/var/named";
...
};
And that path is when you check it as root in your filesystem of course
/var/named/chroot/var/named.
> If you do not include bind-chroot in your system (.....)
Without bind-chroot package installed all paths are equal both for the
bind as on filesystem.
> Thoughts?
>
> David
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2179.nptl
Sirendipity 16:26:32 up 2 days, 23:12, load average: 0.24, 0.37, 0.27
[ ÎÎÏÎÎ Ï'ÎÏÏÎÎ - gnothi seauton ]
my life is a planetarium - and you are the stars
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
