Description of problem: Shutting down the named daemon seems to be forced. Version-Release number of selected component (if applicable): bind-chroot-9.5.0-18.a7.fc8 bind-libs-9.5.0-18.a7.fc8 bind-utils-9.5.0-18.a7.fc8 bind-9.5.0-18.a7.fc8 How reproducible: Fedora 8 with bind installed: $ service named stop Steps to Reproduce: 1. Install Fedora 8 2. Install bind 3. Start Bind 4. Stop Bind Actual results: Can only be killed using the -TERM signal. Should not be needed right? [root@Charlie ~]# service named stop Stoppen van named: ..................................................geen antwoord, stoppen met KILL signaal -TERM [ OK ] Expected results: Exit with a normal termination signal. Additional info: I use it as a chrooted caching server.
Thank you for report, it's bug in initscript. But in standard situation is named stopped with /usr/sbin/rndc utility. I'm not sure why rndc doesn't work in your case. Could you please start named and then run "/usr/sbin/rndc stop" and attach output? Thanks.
Sorry, then I should have posted the named.conf which is now posted anyway (see attachment). I do not have rndc enabled, I use bind as a caching server so no controls needed... . Should I test with rndc anyway?
Created attachment 282771 [details] Config file of named
Created attachment 282791 [details] patch No tests are needed. Initscript wrongly called killproc -TERM function. I've attached patch if you need fix this immediately because I'm going to delay update to more serious issue
bind-9.5.0-20.b1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
Nope, your patch solved it :)