Wicked and Systemd Dependencies
Hello List, I'm just wandering what the current status of wicked during system boot is. As far as I can tell, the network.service unit completes immediately (or after a configurable delay), whether or not network devices have completed their setup. This means that if we want to mount e.g. /usr/local from NFS, we cannot rely on systemd's dependencies. Is this a misconfiguration on my part? Resorting to an arbitrary timeout feels quite clunky. Thanks, A. -- Ansgar Esztermann Sysadmin Dep. Theoretical and Computational Biophysics http://www.mpibpc.mpg.de/grubmueller/esztermann
W dniu 22.03.2021 o 12:09, Ansgar Esztermann-Kirchner pisze:
Hello List,
I'm just wandering what the current status of wicked during system boot is. As far as I can tell, the network.service unit completes immediately (or after a configurable delay), whether or not network devices have completed their setup. This means that if we want to mount e.g. /usr/local from NFS, we cannot rely on systemd's dependencies. Is this a misconfiguration on my part? Resorting to an arbitrary timeout feels quite clunky.
Thanks,
A.
In systemd there is a network-online.target See https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
Ansgar Esztermann-Kirchner wrote:
Hello List,
I'm just wandering what the current status of wicked during system boot is. As far as I can tell, the network.service unit completes immediately (or after a configurable delay), whether or not network devices have completed their setup.
Hi Ansgar network.service is a symlink to NetworkManager.service, so it probably does not make much sense to use that one in a wicked setup.
This means that if we want to mount e.g. /usr/local from NFS, we cannot rely on systemd's dependencies. Is this a misconfiguration on my part? Resorting to an arbitrary timeout feels quite clunky.
How about using an automount? it works really well with systemd. -- Per Jessen, Zürich (4.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
On Tue, Mar 23, 2021 at 12:43 PM Per Jessen <per@computer.org> wrote:
Ansgar Esztermann-Kirchner wrote:
Hello List,
I'm just wandering what the current status of wicked during system boot is. As far as I can tell, the network.service unit completes immediately (or after a configurable delay), whether or not network devices have completed their setup.
Hi Ansgar
network.service is a symlink to NetworkManager.service,
It is link to network service implementation, which is either NM or wicked. What do you think happens when you switch between NM and wicked in YaST?
Andrei Borzenkov wrote:
On Tue, Mar 23, 2021 at 12:43 PM Per Jessen <per@computer.org> wrote:
Ansgar Esztermann-Kirchner wrote:
Hello List,
I'm just wandering what the current status of wicked during system boot is. As far as I can tell, the network.service unit completes immediately (or after a configurable delay), whether or not network devices have completed their setup.
Hi Ansgar
network.service is a symlink to NetworkManager.service,
It is link to network service implementation, which is either NM or wicked. What do you think happens when you switch between NM and wicked in YaST?
(goes all red). Got it. I just took a look at the nearest machine :-) -- Per Jessen, Zürich (5.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.
Andrei Borzenkov composed on 2021-03-23 12:48 (UTC+0300):
Per Jessen wrote:
network.service is a symlink to NetworkManager.service,
It is link to network service implementation, which is either NM or wicked. What do you think happens when you switch between NM and wicked in YaST?
There ought to be three choices: 1 NM 2 Wicked 3 Systemd-networkd http://bugzilla.opensuse.org/show_bug.cgi?id=1183886 -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
participants (5)
-
Adam Mizerski -
Andrei Borzenkov -
Ansgar Esztermann-Kirchner -
Felix Miata -
Per Jessen