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

Aperta
  • Qualcosa non va?
#519 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
47/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, rust
Ambito
devops

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Rust
Stelle
6
Fork
2
Merge medio
1g 3h
PR unite (30g)
42

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di elastos/elastos-runtime

Tutte le issue di elastos/elastos-runtime

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.