openkylin
/
platform_system_core
mirror of https://gitee.com/openkylin/platform_system_core.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity
platform_system_core/rootdir/init.zygote32.rc

17 lines
666 B
Plaintext
Raw Normal View History

Move zygote init config to its own file. This allows us to choose different configs depending on whether or not the target is 64 capable, and what its preferred default is. bug: 13647418 Change-Id: Ie1ce4245a3add7544c87d27c635ee390f4062523
2014-03-31 18:08:02 +08:00
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
class main
Set zygote process priority to -20 to speed up VM startup time. Tests for Nexus9 device shows 450ms boot time speedup, 180ms for Nexus 5X. Bug: 28866384 Change-Id: Icefd130d4bfe5538dae5b9518250807351b0789e
2016-05-19 08:40:41 +08:00
priority -20
give zygote AID_READPROC In zygote wrapping mode, ZygoteConnection does a check to see if the pid reported by the wrapped process is either child process that was forked, or a decendent of it. This requires read access to other processes /proc files. Grant zygote AID_READPROC to allow this access. Bug: 32610632 Test: manual inspection of /proc files to verify group. Test: manual inspection of zygote's children to make sure they do not inherit AID_READPROC Change-Id: I3619a9ae33c8077e068e8024f7c7d44cfca6fb76
2016-11-03 04:35:12 +08:00
user root
Add reserved disk GID to critical component. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Test: builds, boots Bug: 62024591 Change-Id: Ia5af7535cc05a214f8720ac08c594c6db888597a
2018-01-06 08:16:49 +08:00
group root readproc reserved_disk
Move zygote init config to its own file. This allows us to choose different configs depending on whether or not the target is 64 capable, and what its preferred default is. bug: 13647418 Change-Id: Ie1ce4245a3add7544c87d27c635ee390f4062523
2014-03-31 18:08:02 +08:00
socket zygote stream 660 root system
Renamed blastula to unspecialized app process (usap) Bug: 123017829 Test: make & boot & launch apps Change-Id: Id780245f2d86e57cc4964abb2fd10ead9b64da1f
2019-02-23 03:35:08 +08:00
socket usap_pool_primary stream 660 root system
Abort FUSE filesystem when Zygote restarts. The FUSE filesystem is implemented by a Zygote child. If Zygote dies, all of its children die along with it, including the FUSE daemon. The FUSE filesystem is cleaned up automatically whenever the /dev/fuse file descriptor of the FUSE daemon is closed. However, due to the way the binder driver holds on to the 'struct files' of processes in the kernel, the closing of FDs of all of Zygote's children is serialized. That in turn means that, if a process has a file with dirty pages on FUSE, and that FD is closed *before* the FUSE FD, the FUSE kernel driver will happily issue a request to the FUSE daemon to serve that request. But since the FUSE userspace daemon is already dead, it will never get served. And because the closing of all FDs is serialized, we will never close the FUSE fd to unblock this request. Solve this particular case by manually aborting the FUSE filesystem when Zygote restarts. Because we now explicitly close the FUSE fd, the FUSE filesystem will be cleaned up, all outstanding requests to it will be cancelled, and new ones will be skipped. Bug: 153411204 Test: kill zygote manually Change-Id: I2cb6c1a03cc1a932461ff33558894a428ff35180
2020-05-28 22:15:55 +08:00
onrestart exec_background - system system -- /system/bin/vdc volume abort_fuse
Move zygote init config to its own file. This allows us to choose different configs depending on whether or not the target is 64 capable, and what its preferred default is. bug: 13647418 Change-Id: Ie1ce4245a3add7544c87d27c635ee390f4062523
2014-03-31 18:08:02 +08:00
onrestart write /sys/power/state on
Add audioserver uid and restart service when needed Bug: 24511453 Change-Id: I6987a82149d23ad671478cf21488c62cb1ecfc93
2015-10-31 05:17:25 +08:00
onrestart restart audioserver
Restart cameraserver Bug: 24511454 Change-Id: Ia27f4ef0eb71f891c789f637a21b04afe0b1c4e9
2015-12-04 08:32:12 +08:00
onrestart restart cameraserver
Move zygote init config to its own file. This allows us to choose different configs depending on whether or not the target is 64 capable, and what its preferred default is. bug: 13647418 Change-Id: Ie1ce4245a3add7544c87d27c635ee390f4062523
2014-03-31 18:08:02 +08:00
onrestart restart media
onrestart restart netd
Restart wificond when zygote died This helps to avoid tearDownInterfaces call from WiFiStateMachine's constructor. Bug: 33752168 Test: on device Change-Id: I44527ee39700c5ac3259bba3a007dde6979170ff
2016-12-21 03:28:04 +08:00
onrestart restart wificond
Only apply schedTune boost to top-app tasks When using EAS, the foreground tasks were all getting boosted during touchboosts. Limit it to top-app tasks. BUG: 28378389 Change-Id: I72b7158a614bfd9b6c61024774e408ceba61fc9c
2016-05-06 07:10:53 +08:00
writepid /dev/cpuset/foreground/tasks
init/service_parser: Add arguments `window' and `target' for `critical' 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
2019-12-26 22:22:28 +08:00
critical window=${zygote.critical_window.minute:-off} target=zygote-fatal