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

Abierto
  • ¿Algo no está bien?
#518 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
linux, macos, rust
Área
devops, infrastructure

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
6
Forks
2
Merge medio
1 d 3 h
PR fusionados (30 d)
42

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de elastos/elastos-runtime

Todos los issues de elastos/elastos-runtime

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.