07.04.2019 9:15, Mathias Homann пишет:
Am Samstag, 6. April 2019, 22:55:07 CEST schrieb Andrei Borzenkov:
> I had a systemd override file for sddm for a while that stated that > sddm required autofs... but that would basically restart X every > time a network interface went up/down, which does happen every time > you start or stop a VM...
I do not understand how interface up/down is related to service being started/stopped. Care to explain?
/etc/NetworkManager/dispatcher.d contains all kind of scripts that get triggered by interface up/down events. Among others a restart of autofs.
OK, I'll leave the question why autofs is restarted on every up/down to maintainer, but in your case Requires is likely too strong anyway, it is enough to order SDDM after autofs. Not to forget that Requires alone does *not* configure ordering between services anyway.
> Any idea no how to fix it?
Assuming you are using system connection, enable NetworkManager-wait-online.service and set suitable wait time to be sure network is really up.
tried that, didn't work.
This is a bug in openSUSE autofs.service. It should order itself after network-online.target. Upstream does it in sample service since 2015: commit ee7beb818d4919512814b79b04630eda149367a0 Author: Ian Kent <ikent@redhat.com> Date: Wed Jan 21 12:51:03 2015 +0800 autofs-5.1.0 - make service want network-online Wicked startup is synchronous, so it appears to work with it.
...
Anyway, I switched back to wickedd and now all is well again - except I don't have firewalld anymore
Sorry? Of course you have firewalld just as before.
yup. But not as nicely integrated, or can I set the zone for an interface in wickedd as well?
NetworkManager works with connections, not with interfaces. It allows to assign interface where current connection is activated to specific zone based on connection configuration. Do you have different connections with different zones that may be active for the same interface?