Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 154739 - Network manager startup should come up before other network services...
Network manager startup should come up before other network services...
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
Depends On:
  Show dependency treegraph
Reported: 2005-04-13 17:33 EDT by Brian G. Anderson
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-16 16:22:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian G. Anderson 2005-04-13 17:33:20 EDT
Description of problem:
I have a working NetworkManager that automatically connects to my wireless
network when I log in.  However, I get failures during startup because routerd
and ntpd fail because the network isn't up yet.  I'm sure other network services
would fail also.

These services should start after NetworkManager brings up the current connection.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. setup fedora to let network manager start connections, so all interfaces are
disabled on boot
2. reboot
Actual results:
setting network time, ntpd, and starting router discovery failssssss because the
network is not up yet.

Expected results:
These services should be started after network manager brings the connection up.

Additional info:
Comment 1 Dan Williams 2005-05-16 16:22:05 EDT
yep... this isn't going to get fixed until FC5 when we get better initscripts. 
Things dealing with networking right now are quite dumb because we have to
account for network mounted /usr directories, and NetworkManager resides on /usr
(as does hal, dbus, and glib).

Note You need to log in before you can comment on or make changes to this bug.