Comments on: 5 Ways to Keep Remote SSH Sessions and Processes Running After Disconnection

By: Sebastian

Sebastian — Wed, 17 Aug 2022 05:54:30 +0000

Thank you. You and "tmux" just helped to solve my problem.

By: Skeeve

Skeeve — Wed, 16 Mar 2022 10:03:54 +0000

Another solution, which was the only one that worked for me, was to use the “at” command.

I was trying to run a docker container one-off command in the background, but each time I left the server, the process died.

Using
at now «COMMAND
the command here
COMMAND

successfully ran the command in the background.

By: Ravi Saive

Ravi Saive — Thu, 08 Apr 2021 06:07:51 +0000

In reply to Moritz.

@Moritz,

Thanks, corrected the command in the article…

By: Moritz

Moritz — Wed, 07 Apr 2021 14:56:25 +0000

In reply to K. Eriksson. Hey, it is actually disown and not diswon.

By: K. Eriksson

K. Eriksson — Mon, 04 May 2020 12:46:44 +0000

This had the potential to be a really helpful article, but the spelling and editing errors really stacked up and ruined it. I mean, you re-used the same screenshot in #3 when you meant to show us two different things. Very confusing until I figured out it was a mistake. And there's a critical misspelling in one of the code blocks in #4. Running the "diswon" command... how did that work out for you? You have to realize some people are going to be copying and pasting your code blocks directly to their terminals. Have someone run their eyes over your articles and make the edits before you publish them.