Summary: | stopping NM doesn't stop old wpa_supplicant | ||
---|---|---|---|
Product: | Sisyphus | Reporter: | Ivan Zakharyaschev <imz> |
Component: | NetworkManager | Assignee: | Mikhail Efremov <sem> |
Status: | CLOSED WORKSFORME | QA Contact: | qa-sisyphus |
Severity: | normal | ||
Priority: | P3 | CC: | sem |
Version: | unstable | ||
Hardware: | all | ||
OS: | Linux |
Description
Ivan Zakharyaschev
2014-03-20 12:31:24 MSK
The messages from wpa_supplicant appear to be from мар 20 11:49:47, but actually they are from much earlier AFAIU -- these messages come from the initial boot of the system several hours earlier. For some reasons, they were printed to the journal only when I killed wpa_supplicant. (В ответ на комментарий №0)
> NetworkManager should stop the old wpa_supplicant on "service NetworkManager
> stop".
No, it should not. NM withdraw the configuration from wpa_supplicant when it disconnects the interface. But from some point of time NM do not deconfigure interfaces on exit, may be it is the cause. In case of sysvinit I've added workaround in the init script and deconfigure all interfaces before NM is stopped (see NM_STOP_ONEXIT option in the /etc/sysconfig/NetworkManager), but in case of systemd this can't be done so easely (there is no something like ExecStopPre).
Please try to disconnect manually before restaring NetworkManager.service, does it help?
I hope it works nowaday. |