dbus-broker: avoid errors when reloading when /tmp got remounted
When reloading the dbus-broker service (e.g. when switching to a new generation), the reload fails when /tmp got remounted after the service had been started. Since the dbus-broker service starts early, and does not have default dependencies, this situation does occur in practice. This change makes sure that if there are mount units for /tmp, dbus-broker gets ordered after them. See also https://github.com/systemd/systemd/issues/28515
This commit is contained in:
parent
2f1a96018c
commit
c4b3e4f5f8
1 changed files with 5 additions and 0 deletions
|
@ -184,6 +184,11 @@ in
|
||||||
aliases = [
|
aliases = [
|
||||||
"dbus.service"
|
"dbus.service"
|
||||||
];
|
];
|
||||||
|
unitConfig = {
|
||||||
|
# We get errors when reloading the dbus-broker service
|
||||||
|
# if /tmp got remounted after this service started
|
||||||
|
RequiresMountsFor = [ "/tmp" ];
|
||||||
|
};
|
||||||
# Don't restart dbus. Bad things tend to happen if we do.
|
# Don't restart dbus. Bad things tend to happen if we do.
|
||||||
reloadIfChanged = true;
|
reloadIfChanged = true;
|
||||||
restartTriggers = [
|
restartTriggers = [
|
||||||
|
|
Loading…
Reference in a new issue