Missing at least # config: /etc/named.conf # processname: named Alternatively, it is possible to use linuxconf explicitly in a probe command to dynamically parse /etc/named.conf and look at all the configuration files and see if any of them need to be changed. We should probably wait for linuxconf 1.14r1.2 and make bind conflict with linuxconf > 1.14r1.2 (since the probing is for linuxconf to call, if linuxconf is not installed, the probing isn't much of an issue).
I see absolutely no reason to link in any way bind with linuxconf via a dependency/conflct chain. I will fix bind to provide that probing information.
OK, we have discussed this and concluded that bind by definition should know what to do about reloading, and it provides the command "ndc reload" to do intelligent reloading. If bind changes, bind will keep up with its own changes faster than linuxconf can, just by definition. bind does not, however, provide a command to report on its status, which means that to precisely follow probe semantics we would need to always report "reload". We are therefore bending the semantics of the probe statement to always do an ndc reload and never report that anything needs to be done, except if named needs to be started, in which case we will report start. This way, if someone stops named, runs linuxconf to change named configuration, and then exits linuxconf, he will be asked if he wants to start named. Otherwise, named will silently reload.