Yet another daemon init bug. I suppose it's not even the init script this time, but if you have errors in named.conf (like a missing semicolon), and then do /etc/init.d/named start, it says [ OK ].. when actually, it exits. I think i'm noticing a generall problem in daemons here.. apache 1.3 has this problem, and I can't remember all of the other ones I found. Should Gentoo init scripts have process monitoring built into the init scripts? maybe some USE flag like +monitor... that way if a daemon failed, whether because of a faulty config, or a random crash, the init system could possibly 1) realize that 2) do something about it (like restart the daemon, or at least set the state to 'off') Any ideas? Reproducible: Always Steps to Reproduce: 1. 2. 3.
fixed with 9.2.5 thanks, Eric
