Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've started recording of sound (minor CPU, memory and IO load) as

schedtool -R -p 2 -e arecord -f cd > qqq5.wav

And perform large compilation (high CPU load + high memory load + high IO load) as this:

schedtool -D -e nice -n 19 ionice -c3 make

Why does it "overrun!!! (at least -1770319440.252 ms long)" and spoil the recording? Why IDLE_PRIO and idle-io-class dare to mangle tasks with a realtime priority?

How to start heavy-weight thing as really low priority? It is allowed to thrash in a swap as it wants, but without interfering important things!

P.S. and running out of memory to OOM killer certainly produces "overrun!!!" every time...

share|improve this question

You must log in to answer this question.

Browse other questions tagged .