|Summary:||sys-auth/rtkit: warn if kernel has CONFIG_RT_GROUP_SCHED|
|Product:||Gentoo Linux||Reporter:||Jonas Jelten <jj>|
|Component:||[OLD] Core system||Assignee:||Marek Szuba <marecki>|
|Severity:||normal||CC:||hydrapolic, jj, systemd|
|Package list:||Runtime testing required:||---|
Description Jonas Jelten 2015-12-23 21:01:38 UTC
The kernel shouldn't have realtime group scheduling turned on. Otherwise, rtkit won't work. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1229700 where lennart explains it. On my laptop, pulseaudio can get rtscheduling, on my pc group sched is on, and it doesn't work. Please make the users aware of this problem by a ewarn if the config is set. Reproducible: Always
Comment 1 Jonas Jelten 2015-12-23 21:11:06 UTC
The systemd readme recommends this as well: https://github.com/systemd/systemd/blob/ada64a0cff58497147bd856688901f86f86ae1c0/README#L100 Maybe it can directly be added to the systemd ebuild then.
Comment 2 Tomáš Mózes 2015-12-24 07:16:54 UTC
This package currently has no maintainer. If you wish and have time, please provide a patch, we can get this into the tree via the proxy maint team.
Comment 3 Ian Delaney (RETIRED) 2016-02-16 00:34:34 UTC
there has been an expression of interest in this by a user however no comment or patch via Comment
Comment 4 Jonas Jelten 2016-02-16 01:03:11 UTC
Sorry, didn't have time for this and i'm no gentoo dev (yet). Maybe I should try becoming one :) However, I think it's better if systemd itself warns about this, not just rtkit. They recommend this kernel config in their readme as I posted before.
Comment 5 Pacho Ramos 2016-02-20 16:45:10 UTC
I am not sure if this belongs to systemd ebuild or this one (or both) :/
Comment 6 Marek Szuba 2016-02-28 16:55:12 UTC
Created attachment 426926 [details, diff] rtkit-0.11-r1-warn_kernel_rtgroupsched.patch I would say it definitely belongs here - with CONFIG_RT_GROUP_SCHED set rtkit will simply not work unless forced to run as root. As for systemd, the comment in its README is more of a general warning than something specific to it, isn't it? Anyway, please find attached a patch which makes the sys-auth/rtkit check kernel configuration for CONFIG_RT_GROUP_SCHED and produce a warning if that option is set.
Comment 7 Jonas Jelten 2016-03-09 23:18:50 UTC
app-emulation/docker-1.10.0 warns if CONFIG_RT_GROUP_SCHED is _not_ set, so that's kind of a conflict here...
Comment 8 Marek Szuba 2016-03-17 09:45:15 UTC
True, then again having just consulted contrib/check-config.sh in the Docker Github repo, having this kernel feature enabled is optional. It also isn't mentioned at all in the current stable Docker ebuild but that of course can change quite quickly. In the end the matter pretty much grinds down to whether the user prefers to have the Pulseaudio daemon running in real time (it's the only widespread use of rtkit I am aware of) or to have whatever Docker needs this feature for. I would say have both rtkit and docker ebuilds check this, then let the user decide.
Comment 9 Marek Szuba 2016-03-30 11:01:13 UTC
Created attachment 429292 [details, diff] rtkit-0.11-r1-warn_kernel_rtgroupsched.patch Updated the patch to also bump EAPI to 6.
Comment 10 Ian Delaney (RETIRED) 2016-03-30 15:52:34 UTC
FYI, I have made this a revbump to 0.11-r2. This could have been raised and decided in the discussion within irc. Rather than delay it, I have revbumped it on your behalf, this time. Note that with revbumping, all keywords are set to ~arch. commit 9801ab39cd246510f2bd167021d6f6517dfdce91 Author: Ian Delaney <email@example.com> Date: Wed Mar 30 23:46:20 2016 +0800 sys-auth/rtkit: revbump to vn. 0.11-r2 required to effect all changes inherits eclass linux-info, bump to EAPI 6, phase pkg_pretend added to offer to users kernel configuration options. Patch supplied by the proxy maintainer via Gentoo-bug #569546 commit d91cd9c107611aafdd019bb02781f50342b3fa83 Author: Ian Delaney <firstname.lastname@example.org> Date: Wed Mar 30 23:31:23 2016 +0800 sys-auth/rtkit: add proxy user Marek Szuba and g-p-m to metadata.xml User given proxy maintainership of the package by request initially via email via the project's alias. Follow up contact made via irc. Support to be provided by the proxy maintainers project, added to metadata.