can't fix SCHED_OTHER warning

[CaptainBloodz]

media-sound/jack_capture-0.9.73:
Warning. Could not set higher priority for a SCHED_OTHER process using setpriority().

Homebrew kernel full preempt realtime kernel here.
Any kernel config requirements?

Thks 4 ur attention

[kmatheussen]

Hi, that message is not important. Just ignore it. I get it too. :-) If you want to get higher nice values, you can probably fix it by editing /etc/security/limits.conf somehow. I don't remember how.

…

On Mon, Dec 16, 2019 at 11:21 AM CaptainBloodz ***@***.***> wrote: media-sound/jack_capture-0.9.73: Warning. Could not set higher priority for a SCHED_OTHER process using setpriority(). homebrew kernel full preempt realtime kernel here. Any kernel config requirements? Thks 4 ur attention — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#31?email_source=notifications&email_token=AAIX3J6NJWMQ24QI7R24AV3QY5JDVA5CNFSM4J3HSW32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IAWCINA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIX3J74CLIO6JO4PZKHQJLQY5JDVANCNFSM4J3HSW3Q> .

[kmatheussen]

I would guess this line: @users - priority 99 On Mon, Dec 16, 2019 at 11:33 AM Kjetil Matheussen <k.s.matheussen@gmail.com> wrote:

…

Hi, that message is not important. Just ignore it. I get it too. :-) If you want to get higher nice values, you can probably fix it by editing /etc/security/limits.conf somehow. I don't remember how. On Mon, Dec 16, 2019 at 11:21 AM CaptainBloodz ***@***.***> wrote: > media-sound/jack_capture-0.9.73: > Warning. Could not set higher priority for a SCHED_OTHER process using > setpriority(). > > homebrew kernel full preempt realtime kernel here. > Any kernel config requirements? > > Thks 4 ur attention > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#31?email_source=notifications&email_token=AAIX3J6NJWMQ24QI7R24AV3QY5JDVA5CNFSM4J3HSW32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IAWCINA>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAIX3J74CLIO6JO4PZKHQJLQY5JDVANCNFSM4J3HSW3Q> > . >

[CaptainBloodz]

Thks 4 ur prompt reply.
At least I will stop to fiddle around kernel configuration.
Warning remains in master branch... Any reason to keep it?

[kmatheussen]

Maybe not. It should probably only be displayed one time, or if --verbose is specified. It could theoretically prevent disk underruns though.

…

On Mon, Dec 16, 2019 at 2:13 PM CaptainBloodz ***@***.***> wrote: Thks 4 ur prompt reply. Warning remains in master branch... Any reason to keep it? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[CaptainBloodz]

I have little understanding of syscctl thingies & friends.
Should I understand the message as "the current priority of the process is higher than the setting the program is trying to apply", hence the warning?

[kmatheussen]

No it's just trying to set the priority of the disk thread higher than other threads. No big deal. Just ignore it.

…

On Mon, Dec 16, 2019 at 2:26 PM CaptainBloodz ***@***.***> wrote: I have little understanding of syscctl thingies & friends. Should I understand the message as "the current priority of the process is higher than the setting the program is trying to apply", hence the warning? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#31?email_source=notifications&email_token=AAIX3J6C6AC6OH322A2WMPLQY56XJA5CNFSM4J3HSW32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG6WGQY#issuecomment-566059843>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIX3J2PADENU35YWWTB7ADQY56XJANCNFSM4J3HSW3Q> .