Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • The only problem with pausing and resuming processes is that if you made any connections to some other program (like RabbitMQ for instance), the connection would be lost when you resume. Commented Feb 6, 2017 at 23:31
  • @Nav – That's because you didn't run it headless. In bash and zsh, I believe you merely need to disown a backgrounded process. I prefer to run such tasks with nohup or a terminal multiplexer like screen or tmux. You can't pick up a nohup process (just as you can't resume a backgrounded process from a separate connection), but you can connect to a multiplexer. Commented Feb 7, 2017 at 0:37
  • It was a background process. I had closed the terminal and then logged in to the server from another terminal. Commented Feb 7, 2017 at 6:09
  • 1
    @ManuelJordan – You're supposed to use SIGSTOP programmatically and SIGSTP interactively. SIGSTOP cannot be ignored while SIGSTP can. See this answer. Commented May 13, 2022 at 0:48
  • 1
    Very nice. I had set up barrier on two new machines and was sharing a keyboard and mouse. I suspended the barrier client program with ctrl+z from the other machine, and immediately lost control of the machine. Oops. Thankfully a quick google got me here. ssh, ps, and kill -CONT worked the magic! Commented May 15, 2023 at 19:34