Mailinglist Archive: opensuse (1599 mails)

< Previous Next >
Re: [opensuse] ntp and wireless
Will Stephenson wrote:
On Wednesday 28 October 2009 21:00:29 Marc Chamberlin wrote:
Will - I think you are missing the point of this thread. Even if the
NetworkManager does start up the connections before login, the problem
is that it does NOT start them up early enough in the boot up process.
An early startup of the network connections is needed so that other
services which are also starting up, during boot, and dependent on
having the network connections up and running, can also start. NTP is
just one of several daemons that need access to the network, and if it
is not available then it fails to start up.

So far as I know, ifup is the only method that works for these
scenarios. So IMHO the crock is still quite dirty!

I see your point, but in theory dispatcher.d scripts should hup or restart these services after NM brings up the network (since the /etc/init.d/network script does not wait for NM to complete this, unlike when it is in ifup mode).
Also in theory (mine at least) you shouldn't really be using static network mounts or running servers on NetworkManager machines as I doubt that those dispatcher.d scripts, or the services they start/stop, get enough testing to be robust enough in the face of all the dynamism that NetworkManager introduces. Consider a slow-starting server that might not be finished starting in the time between NM bringing a network connection up, and bringing it down again or changing the default route because another network connection it prefers comes up. I'd be sticking to 'desktoppy' network services (SMB ioslaves/GIO) that have more chance of being adapted to NM's signals.

Anyway, I'm just the NM client developer here, not its maintainer. I may be wrong.


Aw! So there is a bit of documentation/insight that I wish I had, when asked to choose which method I wanted to use (in YaST) to manage my network connections! So if I am reading you right, then it appears the goal of the NetworkManager will be to manage network connections in the face of a dynamic network. Somewhat akin to what Windoz Network Neighborhood does now. And yes I would dearly love to be able to browse dynamic networks like I can from Windoz (although I want something far more robust and reliable!!!)

I agree that trying to start and stop, or restart, some services too quickly will cause some of them to fail. (Tomcat immediately comes to mind! LOL) So... let me propose a Grand Unified Network Management project! One that can handle both server systems as well as desktoppy systems!

Uh maybe I should leave now before a shoe hits me in the face....

Marc Chamberlin

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >