Description of problem:
httpd start before named and fails if there are any DNS entries requiring resolution.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the system
2. View /var/log/boot.log
httpd starts before named and fails due to unresolved hostnames.
named starts first and all hostnames are resolved.
The SysV/LSB file includes a dependency on named, but systemd entry does not.
I'm not sure if it's possible to fix it currently, because bind doesn't have systemd unit file yet (see Bug 719419). I will try to find out if it's possible to start named (which still uses LSB init script) before httpd which uses systemd.
Are you sure that you can't refer to SysV init scripts as well? the systemd.service(5) man page says that if a service is requested it will dynamically create a service unit for the script.
Also, if all else fails there is a "SysVStartPriority" option for service units, which is a "temporary compatibility option".
Note that I haven't tried either of these options.
Right, I've found out it should be possible to just use this:
And I've already committed it to rawhide.
I'll try it out as soon as it is available.
httpd-2.2.22-2.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing httpd-2.2.22-2.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
httpd-2.2.22-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.