I am subscribing to PropertiesChanged signal and caching service and its substate in client side. But i noticed that when service is started , i dont get PropertiesChanged signal. how can i update my local client side cache in this case ? my goal is to let my upper layer know when app goes down (running to other substate value)
On Mon, Jul 6, 2015 at 10:03 AM, Pradeepa Kumar <[email protected]> wrote: > Caching the unit's statet is one solution. > But is there any alternative ? > This seems such a basic use case , surprising why there is no easier API > for this ? > On research, I see that some people use JobRemoved signal and on getting > that signal and if it 'done' they check the ActiveState to figure out if > unit went down. > Is this correct way? > What is JobRemoved means? > I am looking for simple and easier way to get notified about unit down. > Thanks for your reply ! > > > > On Fri, Jul 3, 2015 at 4:53 PM, Lennart Poettering <[email protected] > > wrote: > >> On Fri, 03.07.15 16:46, Pradeepa Kumar ([email protected]) wrote: >> >> > When you say 'Check the "state" instead ' >> > Did you mean ActiveState ? >> >> Yes! >> >> Sorry for the confusion! >> >> Lennart >> >> -- >> Lennart Poettering, Red Hat >> > >
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
