On 17/03/16 06:36, Bill Maidment wrote: > Hi guys > Another named update and still the named-chroot.service file has not been fixed. It is really annoying to have to manually fix it every time, just to get DNS working after an update. > Why is the -t /var/named/chroot option included in the ExecStart but not in the ExecStartPre > > ExecStartPre=/bin/bash -c 'if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi' > ExecStart=/usr/sbin/named -u named -t /var/named/chroot $OPTIONS > > Surely named-checkconf should be run with the same named.conf file as named !!! > > This was reported back in November 2015 > https://bugzilla.redhat.com/show_bug.cgi?id=1278082 > This should have been fixed by now. How hard is a one line change to fix ??? This bug has severity set to medium. That means it has most likely not been considered critical enough by Red Hat to go into an errata in the 7.2 life cycle. But as the status is ASSIGNED (not NEW, which is the first status level) - it means someone is working on it. If you do not like this pace, you can log in to the Red Hat customer portal and get in touch with Red Hat support. If you can provide them with good technical arguments why this must be added in the 7.2 life cycle, then you might see this fixed sooner. If you do not have Red Hat subscription with support ... well, then you need to patiently wait. Scientific Linux builds on the source RPMs Red Hat releases. And the reason for these things to take time is that every BZ for RHEL goes through several steps of quality control before a fix gets released. It means Red Hat needs to allocate resources getting these bugs fixed, verified and tested before users see the update. This is the key concept of enterprise distributions, to put efforts into avoiding regressions or new bugs as much as possible and to try to deliver a stable distribution which is properly maintained and updated over many years. -- kind regards, David Sommerseth