Linux: keep Home running after the last SSH logout and start it at boot

Abierto
  • ¿Algo no está bien?
#519 0 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
47/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
linux, rust
Área
devops

Línea de trabajo

The issue names no files or tests. Start by locating the Linux installer, status command, and Home systemd user service, then trace how they handle autostart and uninstall; check related issue #350 for the existing lingering behavior. Done means the documented install modes and status agree, Home starts after logout and reboot when lingering is enabled, and autostart or uninstall leaves lingering unchanged.

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

Descripción

enhancement

Problem

A systemd user service stops when its user's last session ends, and does not start at boot until that user logs in, unless lingering is enabled for the account. On a Jetson or server managed over SSH, Home would still stop at logout and stay down after a reboot. Draft #350 tries to enable lingering and, when that is refused, only prints a warning.

Expected behaviour

  • Install says plainly which mode Home is in: "keeps running after you log out and starts at boot" or "runs only while you are logged in".
  • Where enabling lingering needs an administrator, the installer asks once and explains why. If the person declines or has no admin rights, it shows the single command to run later and finishes the install.
  • Status shows the same mode, so it can be checked later.
  • Autostart off and uninstall change only Home's service, never lingering, since other services on the account may rely on it. If the installer enabled lingering, uninstall says so and shows how to turn it off.

Acceptance

On Linux x86-64 and Jetson:

  • Install over SSH with the admin step accepted, log out of every session, reconnect: Home still works.
  • Reboot without logging in: Home is ready and opens through an SSH tunnel.
  • Install without admin rights: install completes, says "only while logged in" and shows the command; status agrees. After running the command, status reports the new mode without reinstalling.
  • Autostart off, reboot: Home does not start; lingering unchanged.
  • Uninstall: Home's service removed; lingering unchanged; message as above.

Out of scope

macOS (#518). A system-wide service under a dedicated account (#183).

Links

Parent: #518. #350.

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.