Trying to add support of rtkit ona library I'm developping, I'm using rtkit-test from rtkit 0.11 in order to test the rtkit-daemon running on my fedora 21 setup. The daemon is running correctly, but rtkit-test gives the following output: Max realtime priority is: 20 Min nice level is: -15 Rttime limit is: 200000 ns before: SCHED_RESET_ON_FORK: no SCHED_OTHER with nice level: 0 Successfully became high priority. after high priority: SCHED_RESET_ON_FORK: yes SCHED_OTHER with nice level: -10 Failed to become realtime: Permission denied after realtime: SCHED_RESET_ON_FORK: yes SCHED_OTHER with nice level: -10 Why rtkit-test is not given realtime scheduling ? Here's the corresponding activity in the logs: déc. 01 18:04:41 lappc-p348 rtkit-daemon[658]: Supervising 3 threads of 1 processes of 1 users. déc. 01 18:04:41 lappc-p348 rtkit-daemon[658]: Supervising 3 threads of 1 processes of 1 users. déc. 01 18:04:41 lappc-p348 rtkit-daemon[658]: Supervising 3 threads of 1 processes of 1 users. déc. 01 18:04:42 lappc-p348 rtkit-daemon[658]: Successfully made thread 5526 of process 5526 (/home/pacaud/Sources/rtkit-0.11/rtkit-test) owned by '14316' high priority at nice level -10. déc. 01 18:04:42 lappc-p348 rtkit-daemon[658]: Supervising 4 threads of 2 processes of 1 users. I've tested rtkit on a ubuntu trusty box, using rtkit 0.10. It seems to work fine (I get a 'Successfully became realtime' message). Is it a SeLinux related issue ? Seems not, as I don't get alert in the SeLinux alert explorator.
You are most likely running into problems described here. http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime/
Thanks for the pointer. Unfortunatley, I've tried the different workaround listed without success.
Hmm, well yeah...That page is outdated, at least workaround section. We should probably fix that. What you can do is to try assigning realtime budget by writing to cgroup fs manually.
Thanks. I'll try what you propose. I understand this is a workaround, but having to do that sort of things completely defeat the purpose of rtkit, which is to allow some process to get realtime capabilities without tweaking the system settings.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.