Bug 147321
Summary: | named starts too late for programs that need DNS | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Evan Champion <evanchampion> |
Component: | caching-nameserver | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED ERRATA | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | sundaram |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-04 23:54:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Evan Champion
2005-02-07 09:57:49 UTC
Whether named is installed at any runlevel has always been up to the administrator - they must do something like: # chkconfig --level=345 named on # chkconfig --level=0126 named off because the chkconfig line in /etc/init.d/named has always been: # chkconfig: - 55 45 # Meaning that named is not "on" by default in any run level, and is started with order 55, and stopped with order 45. As you point out, many services that require a name service are started before named by default, so the '55 45' positions are not good as defaults . In the next version of named, I will make the chkconfig line: # chkconfig: - 11 89 so it should get started / stopped directly after / before the 'network' service . The traditional behaviour of not being run in any runlevel by default will be preserved. This is now fixed in bind-9.2.5rc1-1 (FC3) / bind-9.3.1rc1-1 (FC4). |