[systemd-devel] StartTransientService problems
Lennart Poettering
lennart at poettering.net
Wed Feb 5 02:07:33 CET 2014
On Fri, 31.01.14 16:42, Barry Scott (barry.scott at onelan.co.uk) wrote:
> I have finally managed to get StartTransientService to run a process for me
> but I'm encountering issues:
>
> we start a daemon that calls StartTransientService as required. The daemon
> does not run as root, it runs as "onelan". We configure dbus to allow
> "onelan" to call all systemd Manager APIs.
>
> I want to set the User, Nice and Type of the service. I get the errors:
>
> DBusException: org.freedesktop.DBus.Error.PropertyReadOnly: Cannot set
> property User, or unknown property.
>
> DBusException: org.freedesktop.DBus.Error.PropertyReadOnly: Cannot set
> property Type, or unknown property.
>
> DBusException: org.freedesktop.DBus.Error.PropertyReadOnly: Cannot set
> property Nice, or unknown property.
>
> What do I need to do to allow these properties to be set?
>
> I also need to set the Environment. I can pass the environment in as a
> property but it does not show up the the process created or in
> systemctl status for the transient service. I do not see any messages in
> the systemd logging.
These options weren't settable so far for transient units, because I was
too lazy to make them settable. ;-)
I have added this in now:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=c7040b5d1c2c148f12b6a5eef3dfce1661805131
Which should make them available via the bus for transient units. If you
need other props like this, just let me know and I'll add them too...
> And lastly what do I have to do to remove the transient service from systemd
> after the last process in the service exits? RemainAfterExit=no
RemainAfterExit=no is already available?
Lennart
--
Lennart Poettering, Red Hat
More information about the systemd-devel
mailing list