Either it be vsftpd, sshd or anything, if NM script is stopped the following messsages will pop up and the service wont start -- WARNING: xxxx is scheduled to start when NetworkManager has started Where xxxx is the name of the service.
Unfortunately, the bug report is unclear. First, please update to networkmanager-0.9.4.0-r4, make sure to merge in the changes in /etc/NetworkManager/dispatcher.d/10-openrc-status, and do /etc/init.d/NetworkManager restart. (This is because 0.9.4.0-r4 fixes several important bugs present in 0.9.4.0-r2.) Second, please precisely describe what steps you are performing, what happens, and what you expect to happen.
Upgrading is going to take some time. Suppose, networkmanager has been stopped and I want to start vsftpd via init scripts -- /etc/init.d/vsftpd start Then, this network service will not start stating -- WARNING: vsftpd is scheduled to start when NetworkManager has started.
(In reply to comment #2) Thanks for clarifying the issue. See http://archives.gentoo.org/gentoo-dev/msg_ab161abd642de7d1b8efa69cf9cd46c3.xml for the conclusion of a long discussion about this on the gentoo-dev mailing list. OpenRC services that require a non-loopback network interface, for example because they need to connect to a remote machine, should have "need net" or "use net" in their init.d scripts. Such services will be run only when a network connection is established (i.e. only when a net-providing OpenRC service is marked as "started"), whether by networkmanager, /etc/init.d/net.*, or whatever other mechanism. OpenRC services that only need a loopback interface, for example because they listen on a local port and run fine whether or not any non-loopback connections had been established, should only have "need lo" or "use lo", not "net". If it makes sense to be able to run vsftpd when no network connections are available, then /etc/init.d/vsftpd should have "need lo" instead of "need net" in its depend() function. I am therefore reassigning the bug to vsftpd maintainers.
As far as I remember, when I started net.eth0/eth1, then also this message (WARNING: xxxx is scheduled to start when NetworkManager has started) was persistent.
Does it really make sense to run a ftp server on loopback? Having a hard time buying that argument.
(In reply to comment #5) > Does it really make sense to run a ftp server on loopback? Having a hard > time buying that argument. Yeah agreed. Closing as WONTFIX
Unfortunately I didn't find an 'unconfirmed' status. vsftp (or in that case any network service) specifically needs networkmanager on my system, i.e. starting net.* (eth1 for e.g.) is not enough. This essentially means, I need a graphical environment to run a networkmanager client in order to start a network service.
(In reply to comment #7) > Unfortunately I didn't find an 'unconfirmed' status. > > vsftp (or in that case any network service) specifically needs > networkmanager on my system, i.e. starting net.* (eth1 for e.g.) is not > enough. > > This essentially means, I need a graphical environment to run a > networkmanager client in order to start a network service. There is an implicit assumption that if you installed networkmanager, it's because you wanted to use it :) However, if you installed networkmanager but do not want openrc to use it as a network provider, simply add rc_provide="!net" to /etc/conf.d/NetworkManager. That will force openrc to use whatever other network providers you have configured (for example, /etc/init.d/net.*) when starting vsftpd and other network services. And if for some reason you want to start vsftpd even when no network providers are enabled, you can add rc_need="!net" to /etc/conf.d/vsftpd
