There is a horrible, at least it was horrible, cron job called "slocate". If you have that cron-job, you should probably turn it off, since it scans the whole HD usually once a day. You can try to run it manually to see what happens: "slocate -u" (as root) On Sat, 12 Jul 2008, Svend-Erik Kjær Madsen wrote: > Dear friends as I said before I'm no techie but I run all my music > applications through PAM and as they all are given nice -19 and rt > permissions I see no problem at all. I only discover problems if I mix > down and have a lot of FX effects in use, let's say over 20. > > > /Sv-e > lør, 12 07 2008 kl. 14:13 +0200, skrev Kjetil S. Matheussen: >> Arnold Krille: >>> >>> Am Donnerstag, 10. Juli 2008 schrieb Kjetil S. Matheussen: >>>> Svend-Erik Kj?r Madsen: >>>>> Now I'm so pleased with my Multiface though it's just a Steinberg >>>>> AudioLink 96 Multiset, I don't regret the money I spend on it, that's >>>>> foe sure. And now I'm pretty confident with the thought of selling out >>>>> my ADAT's and only use my notebook or my stationary computer for music >>>>> recording. >>>> Make sure you turn off cron-jobs, or at least the hardisk >>>> file find updater [1], before doing any important recordings. :-) >>>> [1] Everyone working with audio should probably turn off >>>> that cron job. >>> >>> My big cron jobs check wether "pidof jackd" returns something or not. And if a >>> jackd is running, they don't start... >>> >> >> That's a good idea. But what if the file locate updater cron job >> has started before you start jack? That could be devastating >> if doing a recording of many channels. >> >> _______________________________________________ >> Linux-audio-user mailing list >> Linux-audio-user(a)lists.linuxaudio.org >> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user > >

If the program access the HD, then it makes a difference. PAM can't do anything about that. On Sat, 12 Jul 2008, Svend-Erik Kjær Madsen wrote: > In fact I run no cronjobs at all, but if things are given the right > permission and set propper through PAM there should be no problem > running a script as long as it has lower priority as your music > application as I see it. But thanks for the advise anyway. > > /Sv-e > lør, 12 07 2008 kl. 14:25 +0200, skrev Kjetil S. Matheussen: >> >> There is a horrible, at least it was horrible, cron job >> called "slocate". If you have that cron-job, you should >> probably turn it off, since it scans the whole HD >> usually once a day. You can try to run it manually >> to see what happens: "slocate -u" (as root) >> >> >> On Sat, 12 Jul 2008, Svend-Erik Kjær Madsen wrote: >> >>> Dear friends as I said before I'm no techie but I run all my music >>> applications through PAM and as they all are given nice -19 and rt >>> permissions I see no problem at all. I only discover problems if I mix >>> down and have a lot of FX effects in use, let's say over 20. >>> >>> >>> /Sv-e >>> lør, 12 07 2008 kl. 14:13 +0200, skrev Kjetil S. Matheussen: >>>> Arnold Krille: >>>>> >>>>> Am Donnerstag, 10. Juli 2008 schrieb Kjetil S. Matheussen: >>>>>> Svend-Erik Kj?r Madsen: >>>>>>> Now I'm so pleased with my Multiface though it's just a Steinberg >>>>>>> AudioLink 96 Multiset, I don't regret the money I spend on it, that's >>>>>>> foe sure. And now I'm pretty confident with the thought of selling out >>>>>>> my ADAT's and only use my notebook or my stationary computer for music >>>>>>> recording. >>>>>> Make sure you turn off cron-jobs, or at least the hardisk >>>>>> file find updater [1], before doing any important recordings. :-) >>>>>> [1] Everyone working with audio should probably turn off >>>>>> that cron job. >>>>> >>>>> My big cron jobs check wether "pidof jackd" returns something or not. And if a >>>>> jackd is running, they don't start... >>>>> >>>> >>>> That's a good idea. But what if the file locate updater cron job >>>> has started before you start jack? That could be devastating >>>> if doing a recording of many channels. >>>> >>>> _______________________________________________ >>>> Linux-audio-user mailing list >>>> Linux-audio-user(a)lists.linuxaudio.org >>>> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user >>> >>> > >

nice only controls CPU usage, not HD usage. nice can however make programs that access the HD access the HD a little bit less often, but it will not prevent it from using the HD. For example, try running "slocate -u" with nice 19 and "jack_capture -c 64" with nice -20. You'll see that jack_capture will struggle a lot more using this setup than if you had been running "jack_capture -c 64" with nice 19, and not running "slocate -u" at all. On Sat, 12 Jul 2008, Svend-Erik Kjr Madsen wrote: > If it's set up propper I assume it must wait until it's allowed, if not > please explain how nice are working then .... > > > /Sv-e > lør, 12 07 2008 kl. 14:34 +0200, skrev Kjetil S. Matheussen: > > If the program access the HD, then it makes a difference. > > PAM can't do anything about that. > > > > > > On Sat, 12 Jul 2008, Svend-Erik Kjær Madsen wrote: > > > > > In fact I run no cronjobs at all, but if things are given the right > > > permission and set propper through PAM there should be no problem > > > running a script as long as it has lower priority as your music > > > application as I see it. But thanks for the advise anyway. > > > > > > /Sv-e > > > lør, 12 07 2008 kl. 14:25 +0200, skrev Kjetil S. Matheussen: > > >> > > >> There is a horrible, at least it was horrible, cron job > > >> called "slocate". If you have that cron-job, you should > > >> probably turn it off, since it scans the whole HD > > >> usually once a day. You can try to run it manually > > >> to see what happens: "slocate -u" (as root) > > >> > > >> > > >> On Sat, 12 Jul 2008, Svend-Erik Kjær Madsen wrote: > > >> > > >>> Dear friends as I said before I'm no techie but I run all my music > > >>> applications through PAM and as they all are given nice -19 and rt > > >>> permissions I see no problem at all. I only discover problems if I mix > > >>> down and have a lot of FX effects in use, let's say over 20. > > >>> > > >>> > > >>> /Sv-e > > >>> lør, 12 07 2008 kl. 14:13 +0200, skrev Kjetil S. Matheussen: > > >>>> Arnold Krille: > > >>>>> > > >>>>> Am Donnerstag, 10. Juli 2008 schrieb Kjetil S. Matheussen: > > >>>>>> Svend-Erik Kj?r Madsen: > > >>>>>>> Now I'm so pleased with my Multiface though it's just a Steinberg > > >>>>>>> AudioLink 96 Multiset, I don't regret the money I spend on it, that's > > >>>>>>> foe sure. And now I'm pretty confident with the thought of selling out > > >>>>>>> my ADAT's and only use my notebook or my stationary computer for music > > >>>>>>> recording. > > >>>>>> Make sure you turn off cron-jobs, or at least the hardisk > > >>>>>> file find updater [1], before doing any important recordings. :-) > > >>>>>> [1] Everyone working with audio should probably turn off > > >>>>>> that cron job. > > >>>>> > > >>>>> My big cron jobs check wether "pidof jackd" returns something or not. And if a > > >>>>> jackd is running, they don't start... > > >>>>> > > >>>> > > >>>> That's a good idea. But what if the file locate updater cron job > > >>>> has started before you start jack? That could be devastating > > >>>> if doing a recording of many channels. > > >>>> > > >>>> _______________________________________________ > > >>>> Linux-audio-user mailing list > > >>>> Linux-audio-user(a)lists.linuxaudio.org > > >>>> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user > > >>> > > >>> > > > > > > > >

I wonder if you may be confusing realtime priority with normal priority? "nice" (which controls normal priority programs) doesn't prevent other apps from running once in a while.

If the nice values had mattered, jack_capture wouldn't have struggled at all since jack_capture had maximum priority and slocate minimum priority.

Am Samstag, 12. Juli 2008 schrieb Kjetil S. Matheussen: I either start my computer well ahead of the real recording session (usually I check mails and blogs before), or I start jack before the cron jobs try to run the first time. Or I simply wait till my backup is finished. Its worth the wait... And when its really necessary I login/su to root and stop crond (and with it all its childs). Have fun, Arnold --