Home stops when the terminal or SSH session that started it closes

Offen
  • Stimmt etwas nicht?
#518 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
18/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
linux, macos, rust
Bereich
devops, infrastructure

Rechercherichtung

Read draft #350 and its failed service-removal CI run, then compare the nine changed files against current develop. Trace install locks, data paths, the update controller, and the recovery journal before implementing the Linux systemd user service and macOS LaunchAgent behavior. Run the acceptance journeys on Linux x86-64, Jetson, and macOS; done means service lifecycle, autostart, update/undo, recovery, and uninstall all meet the listed checks.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

documentation enhancement

Problem

In 2.0.0, Home runs only while the terminal that started it stays open. Closing the terminal, or the SSH session on a Jetson or Linux server, stops Home, and updates stop arriving too. The only workaround is tmux or screen.

Expected behaviour

  • The installer registers Home as a background service for the current user (systemd user service on Linux, LaunchAgent on macOS) and starts it.
  • elastos home and elastos home --browser open the running Home, starting it if needed. Closing them leaves Home running.
  • Stop ends the running Home. Autostart on/off changes only Home's own service, never account-wide settings; opening Home with autostart off does not turn it back on.
  • Status shows starting, ready, stopped or failed, with the reason. Ready means this installation's Home and its update controller run, not just that a port answers.
  • If the service cannot start, Home shows the failure and one repair step instead of quietly running in the terminal. Terminal mode stays as an explicit diagnostic option.
  • Update, Undo and interrupted-update recovery never leave two Runtimes or a restart loop.

Scope

Carry the needed behaviour from draft #350 onto current develop: 9 of its 11 files have changed since, and its last CI run failed the service-removal tests. Recheck install locks, data paths, the update controller and the recovery journal. Drop the terminal fall-back; add autostart on/off.

macOS: a LaunchAgent survives closing Terminal but not logout, and starts only at login. Running with nobody logged in needs a system daemon and a separate review.

Docs (INSTALL.md): what keeps running and when; the computer must stay awake; closing an SSH tunnel disconnects the browser but does not stop Home.

Acceptance

On Linux x86-64, Jetson and macOS:

  • Install, close the terminal or SSH session, reconnect: Home works.
  • Kill the Runtime: the service restarts it.
  • Stop: Home stays stopped until opened or the next login.
  • Autostart off: Home does not start at login; elastos home --browser still opens it.
  • Update and Undo: one Runtime afterwards, service still registered.
  • Interrupted update: recovery completes once, no loop.
  • Uninstall removes only this installation's service; data kept unless asked.
  • Linux: the sub-issue's logout and reboot journeys pass.

Out of scope

Tray or desktop app (#394). Isolation and service limits (#183).

Links

#350, failed CI run https://github.com/elastos/elastos-runtime/actions/runs/38211869253, #183, #394.

Vorherrschende Sprache
Rust
Sterne
6
Forks
2
Ø Merge
1 T. 3 Std.
Gemergte PRs (30 T.)
42

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus elastos/elastos-runtime

Alle Issues in elastos/elastos-runtime

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.