On Mon, Apr 24, 2023 at 2:05 PM Charles Rinnoch <lists.opensuse-support@difrenchal.scot> wrote:
Problems come when I try to use Network Manager for the setup at home, in that Network Manager is not invoked [by systemd?] at the same point as Wicked is.
It is.
So that leaves the NFS shares unconnected when the logon screen becomes available [ie the ID's on NFS don't show up] and it appears that Network Manager is more a per user subsystem for which you need to log in in order to get the connections you want.
It is not. Wicked is synchronous, its unit completes startup after interfaces have been configured. NetworkManager is asynchronous - when NetworkManager unit completed startup, it just means the daemon was started. Daemon proceeds to establish connections concurrently with any other startup activity. You need to enable NetworkManager-wait-online.service which will delay followup processing until NteworkManager reports it reached online state. NFS mount points automatically order themselves after network-online.target (which will be after NetworkManager-wait-online.service). If you have some custom units that need network on startup, you need to order them after network-online.target manually.