On 6/15/21 2:30 PM, Ed Greshko wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused with bind/named)
You can see the mounts after starting named-chroot.
Hi Ed,
Is this the case with your zone files in the
chroot directory too?
-T
A fun double check:
Double check that the idondes are the same:
# stat /etc/named.root.key
Device: fd01h/64769d Inode: 60033354 Links: 1
# stat /var/named/chroot/etc/named.root.key
Device: fd01h/64769d Inode: 60033354 Links: 1
# stat /etc/named.conf
Device: fd01h/64769d Inode: 27396278 Links: 1
# stat /var/named/chroot/etc/named.conf
Device: fd01h/64769d Inode: 27396278 Links: 1
inodes match.
:-)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
