Hello,
On Tue, 03 Jul 2018, Walter Dnes wrote:
> Thanks; this could be interesting. Run "ps x", grep for specific
>commands in the output, read the pid at the start of the line, and
>autofreeze those processes..
Use 'pgrep [-u UID/USERNAME] pattern' or adjust ps output to only
display what
Thanks; this could be interesting. Run "ps x", grep for specific
commands in the output, read the pid at the start of the line, and
autofreeze those processes..
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
I just noticed something "interesting". I don't know if it's strictly
gnumeric under ICEWM, or if it's more generic. Open several gnumeric
spreadsheets. Do not minimize, but open one over top of the other. Run
"top" in an xterm in that same workspace...
On Sun, Jul 1, 2018 at 9:40 PM Andrew Udvare wrote:
>
> YMMV on what processes will actually work properly after a SIGCONT. If
> anything a process does is not re-entrant, then you could have very
> unpredictable things happen including corruption of data.
>
If a process corrupts data of any
Den 02. juli 2018 11:34, skrev Vadim A. Misbakh-Soloviov:
>> kill -s SIGSTOP
>> kill -s SIGCONT
> Although, such a "freezing" doesn't free any RAM :-/
>
>
>
It will allow the process to be swapped out without provoking thrashing.
Should work, plugins might give you some grief though.
> kill -s SIGSTOP
> kill -s SIGCONT
Although, such a "freezing" doesn't free any RAM :-/
On Sun, Jul 1, 2018 at 9:16 PM Walter Dnes wrote:
>
> There are some programs that I would much rather keep open, versus
> shutting down and restarting all over again. But keeping them all open
> uses resources, especially on a 10-year-old CORE2 with 3 gigabytes of
> RAM (The thing refuses to
7 matches
Mail list logo
