| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 24/08/12 03:58 PM, William Hubbs wrote: |
| 5 |
> On Fri, Aug 24, 2012 at 01:50:14PM -0400, Alexandre Rostovtsev |
| 6 |
> wrote: |
| 7 |
>> On Fri, 2012-08-24 at 12:10 -0500, William Hubbs wrote: |
| 8 |
>>> The second question this bug brings up is whether services |
| 9 |
>>> should "need" or "use" net. Remember that the "need" dependency |
| 10 |
>>> will try to run the needed service even if it is in init.d but |
| 11 |
>>> not in a runlevel. |
| 12 |
>> |
| 13 |
>> Presumably that depends on the service. If a daemon can deal |
| 14 |
>> with network interfaces going up and down, then "use net" of |
| 15 |
>> course makes more sense. |
| 16 |
> |
| 17 |
> This user is running with pre-configured interfaces (root is nfs |
| 18 |
> mounted). The network interface configuration should not be touched |
| 19 |
> by openrc. |
| 20 |
> |
| 21 |
> If you look at his logs, one issue is that the "network" service |
| 22 |
> is starting even though it isn't in a runlevel. I have made changes |
| 23 |
> in git master so this will not be installed if you do not use the |
| 24 |
> "newnet" use flag. |
| 25 |
> |
| 26 |
> When network interfaces are pre-configured, our network scripts |
| 27 |
> shouldn't run at all, but they can be forced to run if other |
| 28 |
> services have "need net" in their dependencies. |
| 29 |
> |
| 30 |
> So my question is, should we change our services to "use net" |
| 31 |
> instead of "need net"? |
| 32 |
> |
| 33 |
|
| 34 |
No, we shouldn't. "need net" is important and "use net" doesn't |
| 35 |
suffice in many cases. |
| 36 |
|
| 37 |
However, for a NFS-root system there's a way to either #1 make the |
| 38 |
"net" service do nothing (or alternatively overwrite the previously |
| 39 |
configured net with the exact same info -- but iirc the do-nothing |
| 40 |
option works), and alternatively #2 make it so that "net" is provided |
| 41 |
right away. |
| 42 |
|
| 43 |
One thing, though, that i'm not certain of is How the different |
| 44 |
runlevels interact -- ie if "net" is started (considered up) at |
| 45 |
"boot", it should be (and i assume is, but could be wrong) "up" during |
| 46 |
"default" or whatever other runlevel there is, right? I know it was |
| 47 |
with baselayout-1 (which i'm actually still running on my NFS-root |
| 48 |
cluster). |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
-----BEGIN PGP SIGNATURE----- |
| 53 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 54 |
|
| 55 |
iF4EAREIAAYFAlA4J6kACgkQ2ugaI38ACPAoigEAgi/Idi+tk/lmg597aVqJ+dKD |
| 56 |
978sMNwUFnLD5GjTjM4A/1+xa5KmmF9b7SgOw0LFIdcBGByHCq8i3nd3HpgnGYhX |
| 57 |
=FvL9 |
| 58 |
-----END PGP SIGNATURE----- |
Archives