On 06/12/12 18:01, Nick Zivkovic wrote:
So I use many xterms through dwm+xorg.
It happens, sometimes, that I run a computationally (and memory)
intensive program in a different xterm window from the cli, and xorg
eventually becomes completely unresponsive.
Is there a way to tell the Illumos kernel that it absolutely _can't_
just take xorg off the CPU from beneath my feet?
Because once that happens I have no way of killing the computationally
expensive process, and must hard-reboot.
This is the equivalent of a self-inflicted denial of service. What's
worse it can be done unwittingly (if, for example, I didn't write the
code).
one (fairly heavy-weight) approach is to enable the fair-share scheduler
and run computationally intensive jobs in a separate project. See
FSS(7). I've done this for builds and all I can say is that it works
for me..
- Bill
-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com
