since the upgrade to networkmanager-0.9.10.1_pre20141101 boots have been slowed by NetworkManager-wait-online.service failing to start even though NetworkManager was online and the network was up. The boot was blocking on networkmanager-wait-online.service until it timed out. This was never a problem before this version. I have a pretty simple network configuration using dhclient and auto ipv6. I also use vmware-workstation and that starts some bridged devices. After some investigation I tried adding a minimal /etc/NetworkManager/NetworkManager.conf file with contents: [main] plugins=keyfile That fixed the problem and no more hangs or timeouts. It also eliminated some NetworkManager missing plugins warnings The ebuild should check if this file is present and create a minimal one if not.
What is the "systemctl status NetworkManager-wait-online.service" output when it is failing? What was the content of your previous /etc/NetworkManager/NetworkManager.conf that was showing the problem?
the service just says it fails after it times out. There was no NetworkManager.conf file at all previously.
Just to be clear. Our ebuild does not create /etc/NetworkManager/NetworkManager.conf According to what I have read, this file is distribution specific and as of the new versions, seems to be required. Customizations are supposed to go in /etc/NetworkManager/conf.d which is also not created by the ebuild but I think it should be possible to use /etc/conf.d/networkmanager with some changes to the service file. Up until the current version, the missing NetworkManager.conf file caused no problems operationally. As of the new version, a minimal conf file is required for proper operation. I hope this helps.
Please retry with 1.0 (looks to work ok for me... but in my case also the older version worked ok)
After install networkmanager-1.0 and removing the /etc/NetworkManager/NetworkManager.conf file referenced in this bug, I was able to reboot and all went as expected with no extra waiting for the network-wait-online.service. There are some uses for the NetworkManager.conf file for more advanced uses than mine. I am not sure how you want to integrate these use cases into gentoo.
OK, I plan to stabilize 1.0.0 "soon" but will wait a bit for finding new uses (and I am also waiting for a newer evolution-3.12.x version that should be released really soon). Regarding the configuration of NM, in general it should work as-is for most people, I mean, people shouldn't need to make much extra configuration than using the standard tools to configure networks, then, I am not sure if we should do much more :|
What I am concerned about is possible user confusion. do a man networkmanager.conf and compare that to the gentoo handbooks and other network config information. Also there is a /etc/conf.d/networkmanager.conf file in the package that appears to be openrc only and is not in the right format or even referenced by the systemd service. So if you want to do something non-standard which doc do you use and which networkconfig.conf file. That is what I am concerned about.
/etc/conf.d/NetworkManager is on purpose openrc only, systemd unit files get configuration for other places: https://wiki.gentoo.org/wiki/Project:Systemd/conf.d_files
As the wiki link shows, it is still a confusing mess for systemd users. Also, man networkmanager.conf give systemd documentation which could confuse the openrc user. If you don't want lot of bug reports when all of this makes it to stable, something should be either fixed or a least better documented.
