Timeline for How to suspend and resume processes
Current License: CC BY-SA 4.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2022 at 16:29 | comment | added | Rick | 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. | |
| S May 13, 2022 at 8:03 | history | suggested | Manuel Jordan | CC BY-SA 4.0 | Improve presentation |
| May 12, 2022 at 22:38 | review | Suggested edits | |||
| S May 13, 2022 at 8:03 | |||||
| S Feb 14, 2017 at 16:02 | history | suggested | Mark Amery | CC BY-SA 3.0 | fixed a grammar error; removed reference to other answer from first sentence (it's a bit odd now that the answer is below this one) |
| Feb 14, 2017 at 15:52 | review | Suggested edits | |||
| S Feb 14, 2017 at 16:02 | |||||
| S Jan 11, 2017 at 20:37 | history | suggested | Mark Lakata | CC BY-SA 3.0 | Changed confusing wording. end is not the same as stop. |
| Jan 11, 2017 at 19:30 | review | Suggested edits | |||
| S Jan 11, 2017 at 20:37 | |||||
| Dec 27, 2016 at 8:15 | comment | added | AAAfarmclub | See also: [stackoverflow.com/questions/11886812/… | |
| May 2, 2016 at 22:58 | comment | added | Karoh | 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 | |
| S May 1, 2016 at 17:06 | history | suggested | user2943160 | CC BY-SA 3.0 | Move all knowledge related to answer into actual answer (rather than keeping info in the comments) and add my experience with processes being terminated, but remaining in job table. |
| May 1, 2016 at 14:48 | review | Suggested edits | |||
| S May 1, 2016 at 17:06 | |||||
| S Feb 12, 2016 at 10:50 | history | edited | schily | CC BY-SA 3.0 | replace non-standard anmd nonportable kill command line by correct one |
| S Feb 12, 2016 at 10:50 | history | suggested | Jose Gómez | CC BY-SA 3.0 | Updated response with the change suggested in the comments |
| Feb 12, 2016 at 10:48 | review | Suggested edits | |||
| S Feb 12, 2016 at 10:50 | |||||
| Sep 15, 2010 at 22:38 | comment | added | Steve Burdine | @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 :) | |
| Sep 15, 2010 at 22:21 | vote | accept | Stefan | ||
| Sep 15, 2010 at 21:55 | comment | added | ephemient | 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. | |
| Sep 15, 2010 at 21:33 | history | answered | Steve Burdine | CC BY-SA 2.5 |