Le 02/12/2014 12:52, Stoppa, Igor a écrit :
On 2 December 2014 at 13:47, Dominig ar Foll (Intel OTC)
<[email protected]> wrote:
Taeyoung Kim
it is certainly something that would be useful for Tizen.
Likely that time of feature should be linked with a Watchdog service where
services can register a request to be controlled.
(e.g. service xxxx, will send a hart beat every 30s).
Doesn't systemd already provide this?
No Systemd will check that the process is still there, not that it does
provides it service. The model is very common in critical domain where
only a service knows that it is still operational.
e.g. a phone deamon cheking that the model sub system is still alive.
The challenge is to define the policy of what to restart, what to kill when
to force reboot.
That type of configuration should not be done by code and cannot be static.
systemd already knows (or can be taught) the dependency chain
Since it's already part of Tizen, we might as well use it ...
Sorry systemd only knows about the services started by systemd it has no
control on the applications started by the AppFW.
Futhermore restarting a service is often quite different from staring it
as that happens after an error which often let the subsystem in an
unclean state.
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
