11.02.2016 22:11, Patrick Shanahan пишет:
But it still confirms what I suspected. If you now do
systemctl enable wpa_supplicant.service
does connection still drop?
No, wireless connection was maintained.
OK, so here it was happens. By definition "systemctl isolate foo.target" stops all services that would not be pulled in by foo.target. Unfortunately this covers only static dependencies, that can be deduced from Wants/Requires configuration directives. But this does not take in account dynamic socket activated services. Now wpa_supplicant.service is disabled by default, but started on request when D-Bus connection is made. But that also means wpa_supplicant is considered as not belonging to any "run-level" and it is stopped. Feb 07 17:23:35 toshiba dbus[1074]: [system] Activating via systemd: service name='fi.epitest.hostap.WPASupplicant' unit='wpa_supplicant.service' Feb 07 17:23:35 toshiba dbus[1074]: [system] Successfully activated service 'fi.epitest.hostap.WPASupplicant' ... Feb 07 17:24:11 toshiba systemd[1]: Reached target Graphical Interface. ... Feb 09 08:07:22 toshiba systemd[1]: Stopping WPA Supplicant daemon... ... Feb 09 08:08:58 toshiba systemd[1]: Reached target Multi-User System. Stopping wpa_supplicant of course kills wireless connections. This really needs bug report. Brute force workaround is to enable wpa_supplicant service which will add dependency on multi-user.target so wpa_supplicant is no more killed. But it looks like fundamental design issue in systemd ...
systemctl enable wpa_supp.... revealed that there was no sym-link for multi-user.target.
Do we need a bug report?
By all means. But TBH I do not hold my breath - I do not see any way to mark such dynamic service as "in use" ...
ps: terminal where change from graphical to multi-user target was closed.
Yes, this is the same problem.
Is this also a missing sym-link?
Here it is worse. All user sessions run as part of so called "scope" units (look at systemd-cgls output). This scope units are created on the fly. It is simply impossible impossible to add any static dependency from multi-user.target to session-N.scope. And these scope units are apparently stopped as well when you do "systemctl isolate" causing all user processes in this session be stopped. So yes, but report is definitely needed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org