init.d startup script does not find PID file

[mac-tech]

After installing fmDNS with default configs, the init script will report that the service is not running, since the fmDNS moves the PID file out of the default install path:

root@NS1:~# /etc/init.d/bind9 status
 * bind9 is not running

The location of the PID file is controlled in "options" and written in

/etc/bind/named.conf.options 

Setting this option in fmDNS to the ISC BIND default location will solve the problem and report the proper running status:

pid-file "/var/run/named/named.pid";

[WillyXJ]

What OS/distro is this from?

Thanks.

[mac-tech]

Ubuntu 12.04 LTS

Thanks for the great software!

Sent from my iPhone

On Mar 27, 2014, at 9:27 PM, WillyXJ notifications@github.com wrote:

What OS/distro is this from?

Thanks.

—
Reply to this email directly or view it on GitHub.

[WillyXJ]

Reopening to check the auto detection process for Ubuntu.

[WillyXJ]

The default fmDNS installation auto creates a global option of

pid-file "$ROOT/named.pid"

The idea is that it would cover most BIND installations. However, on Ubuntu, the pid file is not in $ROOT so fmDNS expects the user to manually override that in the options configuration for that specific server.

I'm still on the fence about automatically creating a server override based on Linux distro as it could potentially get difficult to maintain.

[WillyXJ]

Added ability to automatically add server config option overrides at client install time. Right now it addresses the pid-file on Debian-based systems. This will be available in v1.2.