26.07.2017 19:24, Michal Hlavac пишет:
Hi,
with new fast laptop I discovered some strange behaviour. After booting docker engine and virtualbox has no internet. I had to restart docker and vboxdrv services. Then it works. And when I stop akonadi before shutdown, it goes very quickly down, but witout stoping I had to wait about minute or more to shutdown.
Is it possible that those services start before network manager on boot or akonadi can't shutdown properly because network is already stopped on shutdown?
akonadi runs as part of user session; there is no direct dependencies between user and system units - rather, all user units implicitly belong to specific system scope unit (which is created for each user session), and are stopped when this scope unit is stopped. As example bor@bor-Latitude-E5450:~/src/linux$ systemctl -t scope UNIT LOAD ACTIVE SUB DESCRIPTION init.scope loaded active running System and Service Manager session-c1.scope loaded active running Session c1 of user bor When this scope unit gets stopped is controller by standard After/Before dependencies bor@bor-Latitude-E5450:~/src/linux$ systemctl show -p After -p Before session-c1.scope Before=shutdown.target After=user-1001.slice systemd-user-sessions.service systemd-logind.service So these scope units will be stopped before systemd-user-sessions.service and systemd-logind.service. if you follow the dependency chain, you will see that there is no direct dependency on any unit that provides networking. I do not say that this is necessary a bug by itself - but huge design issue is that there is no way for a user program to inform systemd that this particular user session needs networking when it is being stopped.
I am asking before I create issue in bugzilla.
Good luck. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org