systemd unit won't persist
See original GitHub issue- Web Browser: Chrome 81.0.4044.129
- Local OS: Windows 10 10.0.18363 Build 18363
- Remote OS: Debian 10
code-server --version
: 3.3.0 52eeccaba1c20279592d790b053639b5ad8ac99d Note: running behind Apache reverse-proxy
Last night, I re-built my development server and installed Code Server 3.3 using the guide provided (thanks!). Previously, I managed it via a systemd service which launched it on start-up and kept it running – the guide now states to use ‘systemctl --user restart code-server,’ which works fine and launches it when the shell is open, but closes it when I close the shell. Is this behavior by design / is there any guidance for keeping it running?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:17 (9 by maintainers)
Top Results From Across the Web
Why won't my enabled systemd service start on boot?
I have no idea why but to get this to work I: deleted Environment=DISPLAY=:%i. added a User= variable. Made sure the correct file...
Read more >systemd unit won't persist · Issue #1673 · coder/code-server
Last night, I re-built my development server and installed Code Server 3.3 using the guide provided (thanks!). Previously, I managed it via a ......
Read more >enabled systemd unit does not start at boot
There must be something else failing. Officially, the way to enable a service on startup in systemd is systemctl enable servicename . Most ......
Read more >Systemd service won't start after reboot [closed]
I've written an example systemd service that executes a Python script that runs every 10 seconds. Python script at /opt/hello.py :
Read more >enabled systemd service not starting
The service starts if i do a systemctl start camtool.service but if i reboot the device, the service is not started.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think I might have fixed it. Tried a reboot with this and works normally now:
sudo loginctl enable-linger username
Sorry for all of the the trouble; appreciate the work you guys put into this.Same behavior with that command. Stays open for as long as the Terminal window is open.