It claims in line 29 : # By default we do not allow hotplugging. But in fact I have to add rc_hotplug="pcscd !net.*" do avoid /lib64/udev/rules.d/90-network.rules to fire up ethernet and wlan
Do you, by any chance, have any net.* services in your runlevels? What about pcscd? is it in your runlevels?
(In reply to William Hubbs from comment #1) > Do you, by any chance, have any net.* services in your runlevels? What > about pcscd? is it in your runlevels? The net are in "default", andpcscd is in "nonetwork" so it is stopped usually: t44 ~ # /etc/init.d/pcscd status * status: stopped (which reminds me to remove it from "nonetwork") Furthermore: t44 ~ # rc-update | grep -e pcs -e net auditd | default nonetwork consolefont | default nonetwork local | default nonetwork net.br0 | default net.enp0s25 | default net.lo | default net.wlp3s0 | default pcscd | nonetwork smartd | default nonetwork syslog-ng | default nonetwork
If the net.* services are in the runlevel, they will be started at that point. The way to tell they were hotplugged is to look at rc-status, and if they show up in the "hotplugged" runlevel they were hotplugged. Also, can you upgrade to 0.18.3 and let me know if this still is happening? Also, look at the fix for #554540 and let me know if that makes the documentation make more sense. I suspect that the documentation issue could be erelated to this bug.
I'm at 0.17 now since awhile which works fine and flawlessly.
