<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Nov 14, 2014 at 3:43 PM, Stef Walter <span dir="ltr"><<a href="mailto:stefw@redhat.com" target="_blank">stefw@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is it intentional (or just laziness :D) that systemd DBus services<br>
like hostnamed, timedated and friends all exit after a timeout even<br>
while callers that have invoked their methods are still on the bus?<br>
<br>
Don't get me wrong, I like services that exit when not in use. But I<br>
sorta imagined 'not in use' as 'no more callers around'.<br></blockquote><div><br></div><div>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.</div><div><br></div><div>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?)</div><div><br></div><div>Maybe the services could have Subscribe() methods to cause them to stick around...</div></div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Mantas Mikulėnas <<a href="mailto:grawity@gmail.com" target="_blank">grawity@gmail.com</a>></div></div>
</div></div>