[GH-ISSUE #40] disconnected during upgrade packages #14

Closed
opened 2026-03-03 13:58:22 +03:00 by kerem · 2 comments
Owner

Originally created by @frederikbosch on GitHub (Jan 16, 2019).
Original GitHub issue: https://github.com/konstruktoid/hardening/issues/40

I am wondering how I can prevent that I get disconnect from ssh when upgrading packages through apt upgrade. This happens when packages have not been updated for a while. Security updates are activated through this installation library, but feature/bug updates will have to be installed manually. And during this process I am disconnected before the installation was finished.

Originally created by @frederikbosch on GitHub (Jan 16, 2019). Original GitHub issue: https://github.com/konstruktoid/hardening/issues/40 I am wondering how I can prevent that I get disconnect from `ssh` when upgrading packages through `apt upgrade`. This happens when packages have not been updated for a while. Security updates are activated through this installation library, but feature/bug updates will have to be installed manually. And during this process I am disconnected before the installation was finished.
kerem closed this issue 2026-03-03 13:58:23 +03:00
Author
Owner

@konstruktoid commented on GitHub (Jan 17, 2019):

If the update takes more than 5 minutes, and gets you disconnected, I suggest you should try running the update using screen or tmux.

<!-- gh-comment-id:455133088 --> @konstruktoid commented on GitHub (Jan 17, 2019): If the update takes more than 5 minutes, and gets you disconnected, I suggest you should try running the update using `screen` or `tmux`.
Author
Owner

@frederikbosch commented on GitHub (Jan 18, 2019):

Thanks, I believe I had problems with that before due to systemctl setting that closed the user session, even when I started tmux/screen. I cannot recall any more. Therefore I close it for now.

<!-- gh-comment-id:455542968 --> @frederikbosch commented on GitHub (Jan 18, 2019): Thanks, I believe I had problems with that before due to systemctl setting that closed the user session, even when I started tmux/screen. I cannot recall any more. Therefore I close it for now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hardening#14
No description provided.