OpenRig
← All of OpenRig 0.7.15

ChangedOpenRig 0.7.15

A slow daemon start now gets three minutes, not 20 seconds, before it's reported pending, and rig daemon start shows its progress about every 20 seconds.

A slow start: rig daemon start now gives the daemon child it started a 180-second readiness budget, instead of 20 s, and prints "Waiting for daemon child <PID> readiness (…s elapsed; 180s limit)" about every 20 s. A quick start still returns at once, and a child that exits ends the wait. Let the wait finish. The budget bounds scheduling: synchronous work can run past the budget. A child still not ready when that budget is exhausted is reported pending as before: "Daemon startup is pending after the readiness deadline". Readiness remains unconfirmed; the child keeps running and the startup reservation is retained. Inspect the address and log it prints, and don't start it again until its restart steps are done: stop the named child PID and wait for it to exit, inspect daemon-start.lock, and only when both recorded launcher and child PIDs are absent, archive the lock and run rig daemon start. rig daemon stop cannot stop that unpublished child.

Pull request
#3118