The earliest point we can start logd is after /system is mounted. Ideally on post-fs-system (does not exist), post-fs will do. As insurance, we will also make sure logd is started if a logd-reinit is requested. This results in logd starting at least 4 processes earlier than it does currently, with a tighter grouping of threads which means we are taking advantage of a lighter CPU load at the time, rather than taking cycles during heavy activity during core startup. Change-Id: If4f0bd3a53bb4c47500a54d741ca635d87c0c330 |
||
|---|---|---|
| .. | ||
| etc | ||
| Android.mk | ||
| init.environ.rc.in | ||
| init.rc | ||
| init.trace.rc | ||
| init.usb.rc | ||
| init.zygote32.rc | ||
| init.zygote32_64.rc | ||
| init.zygote64.rc | ||
| init.zygote64_32.rc | ||
| ueventd.rc | ||