Hi, I have tested it and it is working on git.
I dug this up to figure few things out on shutting down dbus activated services when they are idle. Is it possible that follow up activation request on a service is being ignored by systemd because application has just recently quit? I have this extreme case, - Service shuts down - Dbus gets a signal up on service shutdown (systemd doesn't get SIGCHLD yet) and acknowledges disappearance of the service - An activation request comes up on the service - Dbus sends a dbus signal to systemd to activate the service - Systemd receives the request but is still thinking service is active, so ignores the request - Systemd receives the SIGCHLD and changes the state of service to inactive. This scenario is very unlikely but I am trying to figure out if there are other possibilities. Thoughts? Thanks, Umut On Wed, Jul 2, 2014 at 3:08 PM, Lennart Poettering <[email protected]> wrote: > On Wed, 02.07.14 08:39, Umut Tezduyar Lindskog ([email protected]) wrote: > >> Hi, >> >> I am pretty sure at some point systemd-hostnamed was shutting itself >> down within 5 minutes of inactivity. It seems like we have lost this >> feature. Is the feature removed intentionally? > > Appears to work correctly here. > > Can you check with current git please? I made some changes a while back, > with eec6022cf039e62233139000b9e95db943959e48 and > b27adf354a83ad25f4a209c0a6f7989ecab7b4e2 (maybe others), that fixed > exit-on-idle behaviour. > > Lennart > > -- > Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
