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 (r
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 ou
On Fri, 03.07.15 16:46, Pradeepa Kumar (cdprade...@gmail.com) 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
systemd
When you say 'Check the "state" instead '
Did you mean ActiveState ?
On Jul 3, 2015 3:39 PM, "Lennart Poettering" wrote:
> On Fri, 03.07.15 15:29, Pradeepa Kumar (cdprade...@gmail.com) wrote:
>
> > I am writing lib which will monitor apps and notify/callback higher level
> > if apps went down.
>
On Fri, 03.07.15 15:29, Pradeepa Kumar (cdprade...@gmail.com) wrote:
> I am writing lib which will monitor apps and notify/callback higher level
> if apps went down.
> How can I achieve this?
> I tried doing this using propertieschanged signal and reading
> substate
We reserve the liberty to in
I am writing lib which will monitor apps and notify/callback higher level
if apps went down.
How can I achieve this?
I tried doing this using propertieschanged signal and reading substate
property and that msg does not have old value and new value in the msg.
I noticed that when app go down i get
