Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 650328 - net-misc/networkmanager does not run dispatch scripts on openrc
Summary: net-misc/networkmanager does not run dispatch scripts on openrc
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-12 22:07 UTC by lperkins
Modified: 2018-04-18 18:03 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lperkins 2018-03-12 22:07:11 UTC
NetworkManager running under openrc does not appear to execute any scripts out of /etc/NetworkManager/dispatcher.d  Unfortunately, that includes the script that's supposed to tell openrc that the network interfaces are configured and it can go on with higher level services.  This prevents webservers, etc. from being started without manual intervention.

I've seen this on three independent machine configurations and NetworkManager versions 1.4.4-r1, 1.8.4, and  1.10.2  The only requirement seems to be that NetworkManager and OpenRC be configured to start network interfaces in the background. (I'm not actually sure if it can be forced to wait anymore, I haven't tried to do that in quite a while.  From the looks of the init script the configuration might not matter, but I haven't tested it explicitly.)

I suspect this may be related to: https://bugs.gentoo.org/show_bug.cgi?id=477086  If the dispatcher has been split into a separate service, that service is not listed in /etc/init.d and does not appear to be started by /etc/init.d/NetworkManager

I've chased this about as far as my skill will allow.  I'm not familiar enough with how NetworkManager works to be able to tell for certain if this is a result of the Gentoo configuration or if it's a bug in the NetworkManager program itself.