From: Florian S. <mis...@gm...> - 2007-08-20 08:22:13
|
On Monday 20 August 2007, Richard Cooper wrote: > I had this: > > * hard rtprio 0 > * soft rtprio 0 > pj hard rtprio 40 > pj soft rtprio 20 Mine looks like this: @audio - rtprio 95 @audio - memlock 512000 @audio - nice -19 The memlock is needed for RT programs to lock the memory they use into RAM, so it doesn't get swapped out.. > Aug 20 00:32:01 sucks pam_limits[2639]: unknown limit item 'rtprio' > Aug 20 00:32:01 sucks pam_limits[2639]: unknown limit item 'rtprio' > > ...which is kind of strange since all of the software on the system is new > as of a few days ago, but it seems it doesn't know what I'm talking about. Well, what distribution is that? Or did you build a linux from scratch? I wouldn't recommend that to anyone these days.. Anyways it seems your libPAM is not built with support for the new limits.. > It occured to me to run it like this: > > sudo schedtool -R -p 50 -e su -c "jackd -d alsa -C -P -r 44100 -p 128 -n 2 > -S" pj > > Then it runs with realtime priority, although it isn't aware of the fact, > but it still gets about 5 xruns a second on an idle system, nothing like > the 1 xrun a minute while compiling a program I was getting the other day. Yes this will not do any good. Jack tries to spawn several threads with realtime prio, too. If the process itself doesn't have the right to do so this will fail and you will get xruns.. A good program to inspect all this stuff is e.g. htop [have a look at the sorting [f6] and setup [f2] options].. > I don't know. I'm so tempted to think that it was all just a dream, but > it couldn't have been... It seems you're using an outdated or wrongly built distribution.. Regards, Flo P.S.: You might try coming on #lad on irc.freenode.org. Sometimes it's easier to fix people up with quasi-realtime communications.. -- Palimm Palimm! http://tapas.affenbande.org |