You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What precisely this requires is left to the implementation of the network managing service.
As well as:
Note that networking daemons that simply provide functionality to other hosts (as opposed to consume functionality of other hosts) generally do not need to pull this in.
Since both BlueChi components, controller and agent, require only the DBus to be up and running locally, the ordering on boot can be optimized to After=dbus.service.
Please describe the solution you'd like
The systemd units of bluechi-agent and bluechi-controller are changed to:
To optimize the bluechi-controller and bluechi-agent boot the After
parameter was vhange to dbus.service
Solves: eclipse-bluechi#864
Signed-off-by: Artiom Divak <adivak@redhat.com>
ArtiomDivak
added a commit
to ArtiomDivak/BlueChi
that referenced
this issue
Oct 8, 2024
To optimize the bluechi-controller and bluechi-agent boot the After
parameter was change to dbus.service
Solves: eclipse-bluechi#864
Signed-off-by: Artiom Divak <adivak@redhat.com>
To optimize the bluechi-controller and bluechi-agent boot the After
parameter was change to dbus.service
Solves: eclipse-bluechi#864
Signed-off-by: Artiom Divak <adivak@redhat.com>
Please describe what you would like to see
Currently, the
bluechi-agent
andbluechi-controller
are startedAfter=network.target
. This special target is only weakly defined and there isAs an alternative, network-online.target is mentioned. However, it states there:
As well as:
Since both BlueChi components, controller and agent, require only the DBus to be up and running locally, the ordering on boot can be optimized to
After=dbus.service
.Please describe the solution you'd like
The systemd units of
bluechi-agent
andbluechi-controller
are changed to:The text was updated successfully, but these errors were encountered: