rest: daemon: comment why using a systemd barrier is important for main PID handover
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
parent
0a6df20986
commit
9a1330c72e
|
@ -186,6 +186,8 @@ impl Reloader {
|
||||||
if let Err(e) = systemd_notify(SystemdNotify::MainPid(child)) {
|
if let Err(e) = systemd_notify(SystemdNotify::MainPid(child)) {
|
||||||
log::error!("failed to notify systemd about the new main pid: {}", e);
|
log::error!("failed to notify systemd about the new main pid: {}", e);
|
||||||
}
|
}
|
||||||
|
// ensure systemd got the message about the new main PID before continuing, else it
|
||||||
|
// will get confused if the new main process sends its READY signal before that
|
||||||
if let Err(e) = systemd_notify_barrier() {
|
if let Err(e) = systemd_notify_barrier() {
|
||||||
log::error!("failed to wait on systemd-processing: {}", e);
|
log::error!("failed to wait on systemd-processing: {}", e);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue