On Tue, 08.02.11 12:29, Andrey Borzenkov (arvidj...@mail.ru) wrote:
> > The rtkit patch ensures rtkit itself can get RT privs. This systemd
> > patch ensures apps (such as PA) started within a systemd session can get
> > RT privs. Without neither patch neither side can get RT privs. To work
> > properly both sides need to be able to get RT privs.
> >
>
> Do I need this patch to *strart* rtkit?
Hmm, yes? The cgroup fix needs to be applied when you start rtkit.
>
> {pts/0}% sudo systemctl status rtkit-daemon.service
> rtkit-daemon.service - RealtimeKit Scheduling Policy Service
> Loaded: loaded (/lib/systemd/system/rtkit-daemon.service)
> Active: active (running) since Tue, 08 Feb 2011 12:22:30 +0300; 5s
> ago
> Main PID: 13399 (rtkit-daemon)
> Status: "Running."
> CGroup: name=systemd:/system/rtkit-daemon.service
> └ 13399 /usr/lib64/rtkit-daemon
>
> Feb 8 12:22:30 cooker rtkit-daemon[13399]: Failed to make ourselves
> RT: Operation not permitted
> {pts/1}% systemctl --no-pager --property=ControlGroups show
> rtkit-daemon.service
> ControlGroups=name=systemd:/system/rtkit-daemon.service cpu:/
Uh, oh. Are you suggesting that rtkit does not actually run in the cpu:/
cgroup? Can you verify this with "ps xawf -eo pid,args,cgroup"?
> BTW property name is incinsistent between unit definition and
> systemctl output - ControlGroup vs. ControlGroups. Is it intentional?
Oh, good point. Fixed now.
Lennart
--
Lennart Poettering - Red Hat, Inc.
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
