hive-priv: write a configured stable exe path into unit drop-ins
HIVE_PRIV_EXE, set by the module to the /run/hive-rootfs-check link, is checked at start and used for the drop-in's ExecStartPre. Without it the running binary's path is used as before, and an unlinked one gets an error that names the cause.
This commit is contained in:
parent
cb7a9badf7
commit
ca51bb9d54
1 changed files with 172 additions and 41 deletions
|
|
@ -18,10 +18,10 @@
|
|||
//! never followed. Nothing is deleted or repaired, so whatever is there stays
|
||||
//! for the operator.
|
||||
//!
|
||||
//! The drop-in names the running hive-priv binary, which nothing else roots
|
||||
//! once the system has moved on to a newer build. [`pin_binary`] keeps a GC
|
||||
//! root on it for as long as the drop-in exists, and [`unpin_binary`] drops
|
||||
//! the root with the drop-in.
|
||||
//! With no configured binary the drop-in names the running hive-priv binary,
|
||||
//! which nothing else roots once the system has moved on to a newer build.
|
||||
//! [`pin_binary`] keeps a GC root on it for as long as the drop-in exists, and
|
||||
//! [`unpin_binary`] drops the root with the drop-in.
|
||||
//!
|
||||
//! The entry point is [`run`]; [`check`] holds the rules.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue