https://bugzilla.redhat.com/show_bug.cgi?id=922608
Tomas Hozza thozza@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |thozza@redhat.com
--- Comment #5 from Tomas Hozza thozza@redhat.com --- (In reply to Robert Harker from comment #0)
Additional info: Here are a set of steps I wrote about setting named-chroot in FC18:
# Steps to set up a named in a chroot environment in FC18
# Install the packages yum install bind bind-chroot
"yum install bind-chroot" is enough. bind-chroot Requires bind package, so yum will cover this for you.
# Enable chroot environment # Note: This is a significant change (in FC18)/(relating to systemd) /usr/libexec/setup-named-chroot.sh /var/named/chroot on
# Check chroot environment ls -l /var/named/chroot/etc /var/named/chroot/var/named
# Optional: # You may also want to hard link named.conf and rndc.key from /var/named/chroot/etc to /etc. # Check with ls -li /etc/named.conf /var/named/chroot/etc/named.conf ls -li /etc/rndc.key /var/named/chroot/etc/rndc.key # Create hard links with (ln with no -s) ln /var/named/chroot/etc/named.conf /etc/named.conf ln /var/named/chroot/etc/rndc.key /etc/rndc.key
You don't have to do this at all! named-chroot.service will do everything for you! To all you have to do is just run "systemctl start named-chroot"
# Enable the named-chroot service # Note: If you are running named-chroot.service you do not run named.service # Note: This is a significant change (in FC18)/(relating to systemd) systemctl enable named-chroot.service systemctl start named-chroot.service # Check with systemctl status named-chroot.service
# For ease in named administration add yourself to group named useradd ???
Note: FC18 still uses the rndc command to manage named. Systemd only start/stops the named daemon
systemd can also make BIND to reload it's configuration using rndc for you. All you have to do is type "systemctl reload named-chroot"