On Fri, Aug 24, 2012 at 09:22:15PM -0400, Ian Stakenvicius wrote: > I think this may again come down to the meaning of "net" -- in the > case where rc_depend_strict="no" then "net" just means that the > network interface infrastructure is up and running (ie net.lo); this > should be true and imo is required for something like ssh. When "net" > goes beyond that and includes other interfaces (ie, > rc_depend_strict="yes") then the 'need net' might be a bit strict; on > the other hand if a user has things set up that way then it may very > well be for a reason (for instance, I tend to prefer that sshd is > started after my hotplugged iface is up and likewise goes down when > that iface disappears. I don't see that happening with a "use net" > case when compared against a "need net".
We decided in a previous thread on this list that net.lo should not provide net, and that is how it is set up in ~arch openrc. The part I forgot to change is the network script. We decided that the only things that provide net should be the interfaces that support remote connections (e.g. anything besides the loopback). Also, consider a system where root is nfs mounted or a linux container. If you are running services that "need net" and you have turned off all of the "net" providers by adding something like rc_provide="!net" to their conf.d files, the services that need net will fail hard even though they shouldn't. To handle your sshd case, you could always put rc_need="net" or, even better, rc_need="net.iface" in your /etc/conf.d/sshd file. Thoughts? William
signature.asc
Description: Digital signature
