Am 28.08.24 um 08:58 schrieb Simon Becherer:
Am 28.08.24 um 08:08 schrieb David C. Rankin:
On 8/28/24 12:18 AM, Simon Becherer wrote:
According to the bugreport, only change:
in the file: /usr/lib/systemd/system/wicked.service
section [Unit]
make a new line:
BindsTo=dbus.service
solves it for me.
Hey Simon,
Can you test this for me with your config. Do
# systemctl stop dbus
Does your network also get taken down?
My reading is that if we do BindsTo=dbus.service in wicked.service than any time dbus.service is stopped or crashes, then wicked.service is also stopped automatically.
If that's the case, then I'm not sure we want BindsTo= as a fix. My network is started at boot, it isn't user dependent, so it shouldn't go down if dbus does after it is up and running -- unless there is some other interplay I'm not aware of.
Hi david,
tested at the moment, but i am not able to shutdown dbus:
# systemctl stop dbus
# Failed to stop dbus.service: Operation refused, unit dbus-broker.service may be requested by dependency only (it is configured to refuse manual start/stop). See system logs and 'systemctl status dbus.service' for details.
simoN
Here is a nice explanation (i have not thinked about it what the conclusion is for our usecase): https://pychao.com/2021/02/24/difference-between-partof-and-bindsto-in-a-sys... if you figured out a good solution, let me know. simoN -- www.becherer.de