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*

5
  • 41
    Unless there are other reasons for it, I would prefer SIGTSTP over SIGSTOP, as some applications do handle SIGTSTP specially. For example, if scp is showing a progress bar, SIGTSTP will cause it to clean up the terminal mode before suspending, but if you send SIGSTOP, it will not have a chance to do so. Commented Sep 15, 2010 at 21:55
  • 5
    @ephemient I tried SIGTSTP, I saw what you were saying about it cleaning up the terminal. Thanks for the explanation of SIGTSTP, alawys good to learn new things :) Commented Sep 15, 2010 at 22:38
  • 5
    Also useful to note that you can reference the [pid] value by using the % symbol and then the job number (one that you can find by running jobs). So you'd go: kill -TSTP %1 Commented May 2, 2016 at 22:58
  • 2
    See also: [stackoverflow.com/questions/11886812/… Commented Dec 27, 2016 at 8:15
  • 2
    Why do you mean by it may remain visible there, but terminated ? It's not terminated but stopped/paused. I tried kill -STOP and it behaves exactly like kill -TSTP for shell jobs. Commented Jul 29, 2022 at 16:29