4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	3494548c88	power: the loop and run tests drive their own clock, so a loaded build node cannot starve their timing (flake in #549's check)	2026-10-28 17:12:11 +01:00
jochen	815a55a9fd	power: a lock problem is no longer said once the lock is held	2026-10-05 10:03:30 +02:00
jochen	94d0caa09c	power: the watcher checks its lock is logind's, and takes it again when it is not ... On one server the watcher reported a lock that logind did not list. A descriptor that is not an inhibitor reference is never wrapped (0 would be the bundle's stdin, its channel to the runtime), and every poll checks the lock is still held, taking it again and saying why when it is not.	2026-10-04 17:49:19 +02:00
jochen	6315556152	power: a machine's power as a module holding node-power; the laptop's resume and lid move onto it (hq ADR 0211) ... Code around sleep was written into the service manager's sleep units by the module that needed it, and the mesh could not tell a sleeping machine from a lost one. power runs every module's code for the six moments, each piece bounded, owns logind's power handling from its settings, and says booted, sleeping, woke, shutting-down and the power source on the bus, sleeping under logind's delay lock before the machine sleeps.	2026-10-04 17:19:27 +02:00