-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Add command "loginctl enable-linger $USER" in install.sh #1861
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It might be better to leave this as an option behind a y/n prompt than just do it by default. The enable-linger option has security implications if you're using ssh-agent+keychain or similar tools, and I don't think it should be interfered with silently. |
Let's leave this open until a new release is cut. |
I would recommend systemd stuff not be in the install script at all, since Amazon Linux 2 very deliberately does not include systemd user session support. |
Yes, we're switching to to a system unit so we're fine. |
At least, write it in the documentation |
I install code-server on my ECS by executing
install.sh
.Then execute following:
systemctl --user enable --now code-server systemctl --user start code-server
But when I disconnect the ssh connection from my ECS, the code-server process will be killed immediately and the connection
between ECS and browser will break. Finally, I find this article systemd user instance to solve the problem.
This is solution.
loginctl enable-linger $USER
The issue is only happends when I run code-server as non-root user.
I think you shound add it.
The text was updated successfully, but these errors were encountered: