Bug 595386
Summary: | NETWORKWAIT not documented | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Karl-Olov Serrander <m11172> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | fuzz, iarlyy, jonathan, jpopelka, notting, plautrba, rvokal |
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: | 2010-07-01 16:17:35 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
Karl-Olov Serrander
2010-05-24 14:02:56 UTC
+1 here I'm just looking for answer why dhcpd service does not start at boot if NetworkManager is enabled (bug #565921) and found several bugs where you (Bill) or Dan Williams advise to set NETWORKWAIT in /etc/sysconfig/network. Like in: - bug #441658 - bug #443409 - bug #447036 - bug #447442 - http://blogs.gnome.org/dcbw/2010/04/07/networkmanager-on-server-type-machines-or-why-our-initscripts-suck/ So why is it not documented in sysconfig.txt ? I know NETWORKWAIT is used only by NM and not by initscripts, but where else should it be documented than in sysconfig.txt ? I suggest something like: NETWORKWAIT=yes|no Set to 'yes' to cause NetworManager's initscript to block for 30 seconds or until a network connection is fully brought up. This is useful in scenarios where some service refuses to start during boot if there isn’t network fully up. http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=b3f6e39adc4627af2f781cff87f961246fbe6ac0 Will be in rawhide and likely some future F13 update. |