Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
init.d startup script does not find PID file #79
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
Setting this option in fmDNS to the ISC BIND default location will solve the problem and report the proper running status:
The default fmDNS installation auto creates a global option of
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.