[systemd-devel] How to interact with `systemd --user`?

Kok, Auke-jan H auke-jan.h.kok at intel.com
Thu Jun 14 22:19:52 PDT 2012


On Fri, Jun 15, 2012 at 5:12 AM, Ciprian Dorin Craciun
<ciprian.craciun at gmail.com> wrote:
> On Fri, Jun 15, 2012 at 7:37 AM, Kok, Auke-jan H
> <auke-jan.h.kok at intel.com> wrote:
>> On Fri, Jun 15, 2012 at 4:24 AM, Ciprian Dorin Craciun
>> <ciprian.craciun at gmail.com> wrote:
>>>> I think you really don't want to try and run a systemd --user (highly
>>>> experimental!) without a systemd --system (stable), that would be the
>>>> world upside down, and you're going to get every little part of it
>>>> wrong.
>>>
>>>    I think I'll give it a rest for a while until the `--user` gets more stable.
>>
>> it's stable, but, you're trying to make use of it while it's currently building
>> heavily on assumptions that your system cannot provide, and, you're
>> not providing
>> an appropriate replacement to meet those expectations.
>
>
>    I completely agree that I try to use it in an "special" way
> without having met all the requirements, that `systemd --system`
> gracefully provides.
>
>    Unfortunately I have no choice, as none of these requirements are
> not documented... In the `systemctl` or `systemd` man-page there is no
> single word about any D-BUS related configurations.
>
>    P.S.: To be clearer on my intentions, I try to identify if systemd
> is a good candidate as a process manager for an application composed
> of multiple daemons. Thus when I deliver the application, I want to
> also deliver it with an "embedded" systemd, and not force the client
> to migrate to systemd.

now we're talking!

You can do a ton in that perspective, to make your application more robust
easily and integrate well in systemd.

I'd suggest using socket activation, and looking at some of the examples
that Lennart posted on his blog with example implementation code.

Unfortunately, embedding systemd is untested. While I think it's possible,
and it could just work without a `systemd --system` accompanying it, the
intricacies are indeed not documented well (source code would be the place
for some bits). I've had to poke and even fix code to make some stuff
work.

Cheers,

Auke


More information about the systemd-devel mailing list