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