Bug 480407
| Summary: | initscripts: reorder sysinit scripts to support wireless + kerberos + ldap + autofs | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | W. Michael Petullo <mike> |
| Component: | initscripts | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | initscripts-maint-list, notting, rvokal, vedran |
| Target Milestone: | --- | Keywords: | Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-16 22:09:01 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
W. Michael Petullo
2009-01-16 21:32:32 UTC
That will break (among other things) where ypbind, et. al. are, and I believe there would be a loop created somewhere. Specifically, there's a soft depedency on network in rsyslog, that's done just via numbers, and if you change that, things go bad very quickly. In the long run, it's why dependencies need evaluated dynamically at boot, not statically. WPA in initscripts is a separate bug (154348). As for the rest, until we move to a dynamic system, I doubt this is practical. (In reply to comment #4) > WPA in initscripts is a separate bug (154348). As for the rest, until we move > to a dynamic system, I doubt this is practical. Is this not what upstart was for? In general, yes. For the specific case of SysVinit services, no - it just uses whatever the OS already uses for those scripts. The following order change worked with Fedora 12 Alpha: network 10 -> 24 avahi 96 -> 25 rpcidmapd 18 ->27 The default ordering in Fedora has improved. NetworkManager now initializes network devices and is appropriately started at priority 27. Avahi is started at priority 24 and this works. The only change required is: rpcidmapd 18 -> 27 to ensure rpcidmapd starts after NetworkManager (though both priority 27, r comes after N). I've reopened the bug because fixing this now only requires the analysis of the affect of one priority change, namely rpcidmapd. This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 14 uses: S23NetworkManager S24avahi-daemon S18rpcidmapd S28autofs The ordering of rpcidmapd is suboptimal, as noted in comment #8. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |