Ticket #48 (closed defect: duplicate)

Opened 2 years ago

Last modified 2 years ago

Running init scripts cannot fulfill dependencies if they aren't in a runlevel

Reported by: Donnie Berkholz <dberkholz@gentoo.org> Owned by: roy
Priority: normal Milestone:
Component: rc Version:
Keywords: Cc:

Description

I have net.eth0 and net.wlan0. net.eth0 is in the default runlevel and was stopped. net.wlan0 is not in any runlevel and was started. apache2 refused to use net.wlan0 to fulfill its net dependency. As soon as I added net.wlan0 to the default runlevel, apache2 would use it.

sys-apps/openrc-0.2-r2

Change History

comment:239 Changed 2 years ago by roy

Remove net.eth0 from the default runlevel and allow it to be coldplugged so it still starts automatically at boot. You don't have to allow net.wlan0 to be coldplugged.

With net.eth0 stopped OR inactive, net.wlan0 should satisfy the net dependency when started. This should work fine in openrc-0.2.1.

comment:244 Changed 2 years ago by Donnie Berkholz <dberkholz@gentoo.org>

(In reply to comment #1)

Remove net.eth0 from the default runlevel and allow it to be coldplugged so it
still starts automatically at boot. You don't have to allow net.wlan0 to be
coldplugged.

How can I coldplug services without coldplugging modules? I don't want to load all available kernel modules on my laptop because that sucks the battery dry.

comment:245 Changed 2 years ago by roy

I think udev supports module blacklisting, so blacklist the your wlan module.

comment:246 Changed 2 years ago by Donnie Berkholz <dberkholz@gentoo.org>

(In reply to comment #3)

I think udev supports module blacklisting, so blacklist the your wlan module.

I'll give that a shot. Thanks for the idea.

comment:249 Changed 2 years ago by Donnie Berkholz <dberkholz@gentoo.org>

  • Status changed from new to resolved
  • Resolution set to worksforme

Good enough.

comment:294 Changed 2 years ago by Roger <roger@eskimo.com>

  • Status changed from resolved to reopened
  • Resolution worksforme deleted

FYI: I also have net.eth0 & net.wlan0.

/etc/init.d/nfsmount refuses to use either interface unless both are started. I also believe, if I remove both interfaces from boot or default level, nfsmount still complains by saying it will start once one of the interfaces are up.

From here, it still refuses to start until both are active, even though there is one interface active.

(...probably filed under another bug recently? I'll reopen this bug based on this info?)

comment:296 Changed 2 years ago by Roger <roger@eskimo.com>

I believe bug #33 is a more accurate description of this bug I'm seeing.

Please note, I believe you forgot to mention within your instructions on this page, change "rc_depend_strict=NO" within /etc/rc.conf.

(For historical reasons, mark this bug as a duplicate of bug #33? Bug #33 is also better explanatory then this bug #48.)

comment:298 Changed 2 years ago by roy

  • Status changed from reopened to resolved
  • Resolution set to duplicate

As you wish

Note: See TracTickets for help on using tickets.