[systemd-devel] systemd DBus services exit when they have clients

Mantas Mikulėnas grawity at gmail.com
Fri Nov 14 06:41:52 PST 2014


On Fri, Nov 14, 2014 at 3:43 PM, Stef Walter <stefw at redhat.com> wrote:

> Is it intentional (or just laziness :D) that systemd DBus services
> like hostnamed, timedated and friends all exit after a timeout even
> while callers that have invoked their methods are still on the bus?
>
> Don't get me wrong, I like services that exit when not in use. But I
> sorta imagined 'not in use' as 'no more callers around'.
>

I guess the idea is that many clients (e.g. gnome-settings-daemon) would
make a few calls on startup and then continue running for days without ever
touching the service again.

What are the actual problems caused by this? (I'm guessing something might
rely on `hostnamed` watching /proc/sys/kernel/hostname, or things like
that?)

Maybe the services could have Subscribe() methods to cause them to stick
around...

-- 
Mantas Mikulėnas <grawity at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20141114/b02c39e9/attachment.html>


More information about the systemd-devel mailing list