Description of problem: The default configuration of named does not enable dbus support. I would have expected named to get the '-D' option by default. Version-Release number of selected component (if applicable): bind-9.3.2-20.FC5 bind-config-9.3.2-20.FC5 How reproducible: 100% Steps to Reproduce: 1. install bind and bind-config 2. /etc/init.d/named start 3. notice that named doesn't have dbus support. Actual results: named is run with only "-u named" and without -D by default Expected results: What with NetworkManager and all, I would have expected named to get -D by default in the release. Additional info: Just add this to the default /etc/sysconfig/named file: OPTIONS="-D"
Now fixed with bind-9.3.2-30.fc6 and bind-9.3.2-22.fc5 . The named initscript will now check if the NetworkManager service is enabled in any runlevel, and will then ensure the '-D' option is in $OPTIONS if so.
Can we allow an option override for this via some sysconfig file, so that it stays an option to specify the behaviour to off? Also checking NM in all runlevels looks like a bit too much. Also if -D is alsoready given, all remaining checks could be left away, so that could move to be the first check. regards, Florian La Roche
Yes, the initscript check does already check if -D is already specified. I've now put the test for NM after the test for -D, and added the 'DISABLE_NAMED_DBUS' /etc/sysconfig option - the named.init code to do this is now like this in CVS: --- dbusEnabled=0; for a in $OPTIONS; do if [ $a = "-D" ]; then dbusEnabled=1; fi; done if [ $dbusEnabled -eq 0 ] && [ -z "$DISABLE_NAMED_DBUS" ] ; then NetworkManagerEnabled=0 for l in 0 1 2 3 4 5 6; do if /sbin/chkconfig --level=$l NetworkManager >/dev/null 2>&1; then NetworkManagerEnabled=1; fi; done if [ $NetworkManagerEnabled -eq 1 ]; then OPTIONS="$OPTIONS -D"; fi; dbusEnabled=1; fi --- I'll submit this to FC-6 + FC-5 shortly.
bind-9.3.2-22.fc5 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
Jason, this is fixed ?
It's fixed in bind-9.3.2-33.fc5 / bind-9.3.3-1.fc6