in /etc/rc.conf is the variable rc_hotplug="!net.*" because I don't want to have my network devices 'hotplugged' (I have different runlevels for net.eth0 and net.wlan0. but after reboot rc-status shows the following: Runlevel: hotplugged net.wlan0 [ started ] bluetooth [ started ] udev-postmount [ started ] net.eth0 [ started ] Reproducible: Always Expected Results: that rc-status shows for Runlevel 'hotplugged' only bluetooth and udev-postmount and I have only one concerning active network interface... depending on the runlevel. this was my configuration before updating to 0.4x
I have rc_hotplug commented out entirely and it's not hotplugging them. It's possible there's a logic issue happening inside. Try commenting it out and seeing what happens
I tried commenting out rc_hotplug, but the net.wlan0 and net.eth0 services are still getting started. I have the following line in my /etc/rc.conf: rc_plug_services="!net.eth*" (I want it to only start net.wlan0 on startup, not net.eth0.) This worked prior to upgrading to 0.4.1.
from my point of view it seems to be a problem with the wildcard handling. my workaround (because I have only 2 network interfaces) rc_hotplug="!net.eth0 !net.wlan0"
I actually just tested this with many combinations of devices I didn't want hotplugged (without wildcards), but it still starts their services: Runlevel: hotplugged net.wlan0 [ started ] udev-postmount [ started ] net.eth0 [ started ] I use sys-apps/openrc-0.4.1-r1.
Embarrassingly, this now works. I was setting the wrong variable; rc_plug_services is no more, and rc_hotplug works for me. I apologize for the bugspam.
(In reply to comment #5) > Embarrassingly, this now works. I was setting the wrong variable; > rc_plug_services is no more, and rc_hotplug works for me. > > I apologize for the bugspam. > No worries, closing bug.
