El 18/07/2020 2:59 pm, Andrej Shadura escribió:
Hi,
Thanks for the bug report, but could you please provide more details?
Not sure what extra info is needed. But, let's check some examples:
Machine with Debian 9 and wpa_supplicant service running:
root@nohost:~# systemctl status wpa_supplicant.service
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled;
vendor preset: enabled)
Active: active (running) since Sat 2020-07-18 13:07:36 CDT; 2h 0min
ago
Main PID: 636 (wpa_supplicant)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/wpa_supplicant.service
└─636 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
Produces sockets created in /var/run/:
root@nohost:~# ls -l /var/run/wpa_supplicant/
total 0
srwxrwx--- 1 root root 0 jul 18 13:07 p2p-dev-wlan0
srwxrwx--- 1 root root 0 jul 18 13:07 wlan0
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?
--
Atte. Félix Arreola
«Sin firma GPG»
