wpa_supplicant keeps dir /var/run/wpa_supplicant. This can cause issue if /var/run is mounted as tmpfs. This dir should be created some other way. Reproducible: Always Steps to Reproduce: 1. emerge wpa_supplicant Actual Results: wpa_supplicant keeps dir /var/run/wpa_supplicant Expected Results: wpa_supplicant shouldn't keep that dir
If you remove the directory, does it work like it should?
It's anyway removed after reboot in my case - I have /var/run as tmpfs. I don't know exactly if it would work, I use wicd for wireless with WPA/WPA2 and it works. About using just wpa_supplicant can't say much.
Most everyone has /run (and thus /var/run via symlink) on tmpfs now and this is working fine. wpa_supplicant should not be creating this dir at all, right now it's just creating noise in qcheck when this dir/file go "AFK" after first reboot.
(In reply to Ben Kohler from comment #3) > Most everyone has /run (and thus /var/run via symlink) on tmpfs now and this > is working fine. /run has nothing to do with this bug. It's not standard, and /var/run being symlink is not standard either. It's a lie and full off-topic.
Whoa there, I thought I was on your side, what happened? What I was saying is that LOTS of users already have /var/run on tmpfs (this is the default with current stable openrc) and wpa_supplicant is still working just fine, so we don't need to keepdir. I'm not trying to be off-topic or lie to anyone.
Fixed, I have removed it from 2.1-r1 - no reason to bug to -r2 for this, since it makes no difference for the people already on 2.1-r1