45215ae6e5
The critical services can now using the interface `critical
[window=<fatal crash window mins>] [target=<fatal reboot target>]` to
setup the timing window that when there are more than 4 crashes in it,
the init will regard it as a fatal system error and reboot the system.
Config `window=${zygote.critical_window.minute:-off}' and
`target=zygote-fatal' for all system-server services, so platform that
configures ro.boot.zygote_critical_window can escape the system-server
crash-loop via init fatal handler.
Bug: 146818493
Change-Id: Ib2dc253616be6935ab9ab52184a1b6394665e813
16 lines
666 B
Text
16 lines
666 B
Text
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
|
|
class main
|
|
priority -20
|
|
user root
|
|
group root readproc reserved_disk
|
|
socket zygote stream 660 root system
|
|
socket usap_pool_primary stream 660 root system
|
|
onrestart exec_background - system system -- /system/bin/vdc volume abort_fuse
|
|
onrestart write /sys/power/state on
|
|
onrestart restart audioserver
|
|
onrestart restart cameraserver
|
|
onrestart restart media
|
|
onrestart restart netd
|
|
onrestart restart wificond
|
|
writepid /dev/cpuset/foreground/tasks
|
|
critical window=${zygote.critical_window.minute:-off} target=zygote-fatal
|