Skip to content

Prevent KeepAlive respawn during boot-service migration - #74

Merged
kudama merged 1 commit into
mainfrom
fix/boot-service-keepalive-stop
Nov 16, 2026
Merged

kudama merged 1 commit into
mainfrom
fix/boot-service-keepalive-stop

Conversation

@kudama

@kudama kudama commented Nov 16, 2026

Copy link
Copy Markdown
Owner

The initial Foundry migration signalled the controller and waited for it to stay stopped, but launchd immediately respawned its KeepAlive job. The installer timed out and rolled back before system jobs were installed. Unload KeepAlive jobs with bootout so launchd handles shutdown without respawning; retain Curator’s successful SIGINT exit before unloading.

2026-11-15: rollback health confirmed for all three login services, no active Forge/Curator jobs. Five focused tests pass including a KeepAlive regression. The corrected stop/restore sequence was exercised on actual Foundry: all three unloaded without respawn, unchanged login definitions restored, authenticated Forge and Ollama ready, all 4,303 Curator task records unchanged. Administrator system installation and reboot acceptance remain pending. Refs #72.

@kudama
kudama merged commit a5662d0 into main Nov 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant