[systemd-devel] User systemd unit files

[Chris Morgan]

On Mon, Sep 8, 2014 at 3:30 PM, Mantas Mikulėnas <grawity at gmail.com> wrote:
> On Mon, Sep 8, 2014 at 9:27 PM, Chris Morgan <chmorgan at gmail.com> wrote:
>> Hello.
>>
>> We have a build environment that we use to build our software for
>> desktop Linux and we are currently using Yocto to build for an
>> embedded target.
>>
>> I'm looking for a way for developers to use the systemd unit files for
>> our services out of their user owned build directory during
>> development so we can use the same files during development that we
>> would use during production.
>>
>> I came across 'systemd --user' but I'm not having much luck starting
>> this up as my own user as it looked like $SYSTEMD_UNIT_PATH was
>> exactly what I was looking to set.
>>
>> Fedora 20 cli output:
>>
>> $ /usr/lib/systemd/systemd --user
>> Failed to create root cgroup hierarchy: Permission denied
>> Failed to allocate manager object: Permission denied
>>
>> And some discussion on libreoffice pages seems to be indicating that
>> 'systemd --user' isn't supported any more.
>
> Specifically, running `systemd --user` directly is not supported
> anymore. The user mode still works, but only for one "user" instance
> per UID, launched through user@<uid>.service (recent releases start
> this automatically upon logging in).
>
> --
> Mantas Mikulėnas <grawity at gmail.com>


Would support for the single user instance support what we are looking
to do with our build setup?

I'm open to mostly any approach but I'd prefer to use the unit files
directly rather than a second script just for starting things up on
the desktop environment. Plus it would let us test things like
automatic service restart, logging etc.

Chris