Linux: keep Home running after the last SSH logout and start it at boot
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Rust
- 星标
- 6
- 派生
- 2
- 平均合并
- 1 天 3 小时
- 30 天内合并 PR
- 42
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
elastos/elastos-runtime 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
elastos/elastos-runtime#563 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
elastos/elastos-runtime#508 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
elastos/elastos-runtime#436 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
elastos/elastos-runtime#427 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
elastos/elastos-runtime#405 ·
维护者通常 1 天内回复
查看 elastos/elastos-runtime 的全部 Issue
相似的 Issue
-
bug good first issue help wanted linux macos testing
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
area: app type: test
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
bug priority: medium
难度 2/5 1-3 小时 新手友好度 78/100
storytold/photocraft#12706 · 1 条评论 ·
维护者通常 1 天内回复
-
bug priority-low to-agent
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
examples/dca and limit-order: swap always fails on the real Soroswap router (deadline equals now)未关闭
难度 2/5 1-3 小时 新手友好度 76/100
sorocon-labs/sorocron#172 ·
维护者通常 1 天内回复