Why does bind named have a double chroot?
Issue
- When named is started, it appears to create 2 chroot environments:
[root@localhost named]# pwd /var/named/chroot/var/named/chroot/var/named - The chroot directories even have the same inode number:
[root@localhost named]# ls -1id /var/named/chroot /var/named/chroot/var/named/chroot 403251 /var/named/chroot 403251 /var/named/chroot/var/named/chroot
Environment
- Red Hat Enterprise Linux 6
- bind-chroot-9.7.3-2.el6_1.P1.1.i686
- bind-9.7.3-2.el6_1.P1.1.i686
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
