jschoubben
6724dab0cf
mesh/delivery merged: source.main moved to novox/mesh-catalog@58309a972945
mesh/delivery-group group fix/shutdown-bound merged: every member is merged
mesh/check pass 6724dab0cf96 on 387ee59140c4 | unit 2192 run, 3794 kept, 57 skipped | integration 2208 run, 3829 kept, 57 skipped | over bound: unit, …
On ace's reboot of 2026-10-28 every unit had stopped within 17 s, yet the bus and polkit were started again during the shutdown, nothing stopped them a second time, and the reboot waited on reboot.target's 30-minute job timeout, silent, until the operator forced it. node-power owns the shutdown on every machine, so its drop-ins on reboot, poweroff and halt shorten the bound; each target keeps its own forcing action, so the last phase still ends every process, unmounts and syncs. The cause, node-tools starting bundles again while it stops, is fixed in mesh-tools.
9 lines
504 B
Plaintext
9 lines
504 B
Plaintext
# Written by the mesh (module power, novox/hq ADR 0211; issue 1126). Replaced on every push.
|
|
#
|
|
# A shutdown is bounded at ten minutes, not systemd's thirty. A unit started again during the shutdown
|
|
# (on ace, 2026-10-28, the bus and the authorization manager) is never stopped a second time, and the
|
|
# shutdown then waits on this job's timeout with nothing on the console. The target keeps its own
|
|
# forcing action: the last phase still ends every process, unmounts and syncs.
|
|
[Unit]
|
|
JobTimeoutSec=10min
|