| 1 |
On Sun, Jul 1, 2018 at 9:16 PM Walter Dnes <waltdnes@××××××××.org> wrote: |
| 2 |
> |
| 3 |
> There are some programs that I would much rather keep open, versus |
| 4 |
> shutting down and restarting all over again. But keeping them all open |
| 5 |
> uses resources, especially on a 10-year-old CORE2 with 3 gigabytes of |
| 6 |
> RAM (The thing refuses to die). Is there a way to forcibly swap out or |
| 7 |
> freeze a specific PID, until I need to get back to it again? |
| 8 |
> |
| 9 |
|
| 10 |
kill -s SIGSTOP <list of PIDs> |
| 11 |
|
| 12 |
to resume: |
| 13 |
|
| 14 |
kill -s SIGCONT <list of PIDs> |
| 15 |
|
| 16 |
man kill |
| 17 |
man 7 signal |
| 18 |
|
| 19 |
YMMV on what processes will actually work properly after a SIGCONT. If |
| 20 |
anything a process does is not re-entrant, then you could have very |
| 21 |
unpredictable things happen including corruption of data. |
| 22 |
|
| 23 |
Andrew |
Archives