On 10/25/07, <b class="gmail_sendername">Florian Schmidt</b> <<a href="mailto:mista.tapas@gmx.net">mista.tapas@gmx.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 24 October 2007, Chuckk Hubbard wrote:<br>> On 10/24/07, Florian Schmidt <<a href="mailto:mista.tapas@gmx.net">mista.tapas@gmx.net</a>> wrote:<br>> > if you run<br>> ><br>> > sudo chrt -fp 70 `pidof "jackd"`
<br>> ><br>> > as non root without using sudo<br>> ><br>> > chrt -fp 70 `pidof "jackd"`<br>> ><br>> > do you get an error?<br>><br>> Why no I don't! And it changes priority. I swore it didn't work before
<br>> when I tried it. I've just now added "session required<br>> /lib/security/pam_limits.so" to /etc/pam.d/common-session, as others<br>> suggested, maybe that did something?<br>> So does that mean the -P flag can never set priority 70? I got it from
<br>> your site!<br><br>Well, if chrt works now without sudo, try running<br><br>jackd -R -P 70 -d alsa ...<br><br>again. It should work now, too..</blockquote></div><br>Update: I just discovered that running jackd -R -P 70 -dalsa -P -p256 -n2 -r44100 as ROOT doesn't even set priority 70. jackd then runs as a root process with priority 20, according to both chrt and top.
<br clear="all">Apparently my system is not able to run anything higher than 20 priority; does this mean my kernel is misconfigured, or might it be something else?<br>-Chuckk<br><br><br>-- <br><a href="http://www.badmuthahubbard.com">
http://www.badmuthahubbard.com</a>