I rebooted my system today after making a few changes to my named.conf and the usual sequence of showing all the services being brought up happened as normal. However, I had made an error in my named.conf file and as such named did not start. I fixed the problem and tried to start Bind manually using /etc/init.d/named start, but it kept complaining that named was already running. On checking rc-status, it stated that named had been successfully started. Given that named was quite clearly not running ('ps aux | grep named' returned no output other than 'grep named'), this is incorrect. The only way to fix the problem was to reboot the whole machine, which is not really practical because it means if named has a problem I have to restart everything else as well (Apache, postfix etc). I've run into this problem several times before, but it was only this time that I realised that it was rc-status that was causing the problem. Reproducible: Always Steps to Reproduce: 1. Make a mistake in named.conf (e.g. in this case putting Access Control Lists in the wrong section) 2. Run /etc/init.d/named start Actual Results: Error message stating that named was already started. Expected Results: Started named.
the other workaround is to rm /var/lib/init.d/started/named
that's fixed somewhere around 9.2.5/9.3.1 thanks for report, Paul
