[systemd-devel] Systemd socket activation of DBus in the user session
Kok, Auke-jan H
auke-jan.h.kok at intel.com
Mon Jun 18 23:49:27 PDT 2012
On Tue, Jun 19, 2012 at 5:17 AM, Kok, Auke-jan H
<auke-jan.h.kok at intel.com> wrote:
> On Mon, Jun 18, 2012 at 5:22 PM, Peeters Simon <peeters.simon at gmail.com> wrote:
>>>> also i have been running the patch succesfully (both in system mode
>>>> and in my systemd-gnome-session (which i will share soon)) for a while
>>>> now (read: since last week) without any problem.
>>>
>>> ah nice! is that on systemd HEAD? Love to see the code :^)
>>
>> systemd-185-3.fc18, i dont like building a lot of stuff (poor atom cpu)
>>
>> the idea is based on your code, but split up in 3 parts:
>> - the main daemon: starts session prepares for X and launches systemd
>> as user (the daemon itself stays root)
>
> Argh!
>
> So you run a daemon as root. Do you pam_open_session() and all?
>
> I'm running into this:
>
> systemd[1]: Failed to create cgroup cpu:/: No such file or directory
> systemd[4393]: Failed at step CGROUP spawning
> /usr/lib/systemd/systemd: Invalid argument
<snip>
Turns out I had somehow lost CONFIG_CGROUP_SCHED=y
I started digging in git for the documentation about kernel options,
obviously, there is none :(
Auke
More information about the systemd-devel
mailing list