Hi, On Sat, 18 Jul 2020, at 22:14, APT Gatuno MX wrote: > Machine with Debian 10 and wpa_supplicant refreshly restarted: > > root@malistand:~# systemctl status wpa_supplicant.service > ● wpa_supplicant.service - WPA supplicant > Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; enabled; > vendor preset: enabled) > Active: active (running) since Sat 2020-07-18 15:10:00 CDT; 2s ago > Main PID: 2913 (wpa_supplicant) > Tasks: 1 (limit: 2222) > Memory: 756.0K > CGroup: /system.slice/wpa_supplicant.service > └─2913 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant > > Please note that the command is run with the same options. And the > result of /var/run/wpa_supplicant: > > root@malistand:~# ls -l /var/run/wpa_supplicant > ls: no se puede acceder a '/var/run/wpa_supplicant': No existe el > fichero o el directorio > > These sockets are control interfaces. They are unix socket, that can be > used by other applications to 'control' wpasupplicant. > > I'm happy to provide more info, what else is needed?
Could it be that /var/run is for some reason not a symlink to /run? Please note that the socket directory is in fact in /run. It would be strange, but let's eliminate that before we go deeper in the investigation :) -- Cheers, Andrej
