Tracking F5 / daemonization from docs/plans/v3.2-prove-it-plan.md.
README: Background daemonization is Not implemented. --background exits non-zero with guidance. Users need a launchd/systemd unit or a terminal they never close.
Maintainer decision (v3.2 plan §8): unit files, not double-fork. Double-fork does not survive reboot, and every user who wants a daemon wants it to survive reboot. True double-fork stays deferred.
Work (61-02)
memory-daemon install-service writes a launchd plist (macOS) or systemd user unit (Linux) and loads it, plus uninstall-service.- Keep
--background exiting non-zero, now pointing at install-service.
- Verify in the bats suites on both Tier 1 platforms.
Neither main nor the March orphan line has install-service today.
Tracking F5 / daemonization from docs/plans/v3.2-prove-it-plan.md.
README: Background daemonization is Not implemented.
--backgroundexits non-zero with guidance. Users need a launchd/systemd unit or a terminal they never close.Maintainer decision (v3.2 plan §8): unit files, not double-fork. Double-fork does not survive reboot, and every user who wants a daemon wants it to survive reboot. True double-fork stays deferred.
Work (61-02)
memory-daemon install-servicewrites a launchd plist (macOS) or systemd user unit (Linux) and loads it, plusuninstall-service.--backgroundexiting non-zero, now pointing atinstall-service.Neither
mainnor the March orphan line hasinstall-servicetoday.