Uh, don't run your computationally expensive process with real-time or fixed privileges? In a *normal* situation you should never have to do any of this, even in the face of CPU hogs.
You probably can use pbind to bind your Xorg process to a CPU and to limit which CPUs the "computationally expensive" process is allowed to run on, assuming you have multiple CPUs (virtual CPUs that is...) Garrett D'Amore [email protected] On Jun 12, 2012, at 6:01 PM, 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). > > Thanks. > > -- > :. > Blog: nickziv.wordpress.com > Twitter: www.twitter.com/nickziv > > > ------------------------------------------- > illumos-discuss > Archives: https://www.listbox.com/member/archive/182180/=now > RSS Feed: https://www.listbox.com/member/archive/rss/182180/22003744-45f01c1f > Modify Your Subscription: https://www.listbox.com/member/?&; > Powered by Listbox: http://www.listbox.com ------------------------------------------- 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
