-
Notifications
You must be signed in to change notification settings - Fork 313
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
Feature Request: Shutdown remote server after disconnect #10205
Comments
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Thanks for the idea. This kind of action might be better performed by the user outside of Remote - SSH extension (I am assuming from context you're using that extension). You didn't mention what platform you are on, but here's an idea on linux on how you could accomplish what you're looking for. |
Indeed, I am using Remote-SSH extension, and logging into a minimal but persistent Linux container. Killing the remote server in an outside script has the problem that if a user logs out from a terminal session, it might kill a server that is still connected to VSCode. |
It looks like #440 achieves the same thing as this request (with a small timeout). If so, you can close this issue. |
This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation. Happy Coding |
🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
After disconnecting from a remote, it would be good to shutdown remote servers automatically. These services consume several Gigs of RAM, so it isn't ideal to have them running around for long.
If there was a way to configure the shutdown period, that would be nice. Then people who need the servers lingering can keep a high timeout value. While those who would like to conserve memory on the remote can set a lower timeout.
The text was updated successfully, but these errors were encountered: