This service fails to start on a my machine with a nfs network root mounted filesystem: Service `mythbackend' needs non existent service `net' Reproducible: Always
Well you should not have a non existent service on net. That's not what the tracker that you referred to is about. Future versions will move the need into the configuration file. The issue you're seeing is unrelated.
(In reply to comment #1) > Well you should not have a non existent service on net. That's not what the > tracker that you referred to is about. Future versions will move the need > into the configuration file. > > The issue you're seeing is unrelated. I'm not sure what you mean. The interface already exists since a nfs root filesystem boots off the network. Since the network interface already exists, openrc should not try to bring it up or down which is why I have this in /etc/conf.d/network: rc_provide="!net" These latest changes to openrc do not allow me to bring up any service that specifies need net in the init script until the need net line is removed or rc_need="!net" is specified in that service's configuration file. In these future versions you're referring to, are you're saying that I will need to disable this need net in every configuration file for each service that specifies need net for a machine with a network mounted nfs root filesystem?
(In reply to comment #2) > (In reply to comment #1) > > Well you should not have a non existent service on net. That's not what the > > tracker that you referred to is about. Future versions will move the need > > into the configuration file. > > > > The issue you're seeing is unrelated. > > I'm not sure what you mean. The interface already exists since a nfs root > filesystem boots off the network. Since the network interface already > exists, openrc should not try to bring it up or down which is why I have > this in /etc/conf.d/network: > > rc_provide="!net" Right. You're using the supposed "newnet", which is really just BSD style configuration which is broken for a dependency based init system. And disabling the one thing that newnet is able to provide is not correct, hence the configuration is invalid.
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > Well you should not have a non existent service on net. That's not what the > > > tracker that you referred to is about. Future versions will move the need > > > into the configuration file. > > > > > > The issue you're seeing is unrelated. > > > > I'm not sure what you mean. The interface already exists since a nfs root > > filesystem boots off the network. Since the network interface already > > exists, openrc should not try to bring it up or down which is why I have > > this in /etc/conf.d/network: > > > > rc_provide="!net" > > Right. You're using the supposed "newnet", which is really just BSD style > configuration which is broken for a dependency based init system. And > disabling the one thing that newnet is able to provide is not correct, hence > the configuration is invalid. William mentioned that this is needed in addition to rc_need line in the conf.d configuration file in bug 425130. Is rc_provide="!net" not needed then and only rc_need="!net" in this scenario?
Created attachment 391520 [details] mythbackend.init Removed need net from mythbackend init script
Sorry for the long delay but this will be addressed in the next 0.27.5 bump.
Thanks for the report. Fixed in http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9ada29b52010e465a522fdc68d4eee0da6eaa349
