diff options
| author | Mark Salyzyn <salyzyn@google.com> | 2015-04-07 15:32:12 -0700 |
|---|---|---|
| committer | Mark Salyzyn <salyzyn@google.com> | 2015-04-08 09:18:50 -0700 |
| commit | 124ff15bcaeded8b794e18bd1523e3affa97c386 (patch) | |
| tree | 316d0f6b0bd5c6ad6f1a694025ce4fc78ac5faa6 /rootdir | |
| parent | bf403968878fca07c6df98852e8958ddda365bab (diff) | |
| download | system_core-124ff15bcaeded8b794e18bd1523e3affa97c386.zip system_core-124ff15bcaeded8b794e18bd1523e3affa97c386.tar.gz system_core-124ff15bcaeded8b794e18bd1523e3affa97c386.tar.bz2 | |
rootfs: init start logd in post-fs
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
Diffstat (limited to 'rootdir')
| -rw-r--r-- | rootdir/init.rc | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/rootdir/init.rc b/rootdir/init.rc index 0edb984..e6f4f4a 100644 --- a/rootdir/init.rc +++ b/rootdir/init.rc @@ -188,6 +188,7 @@ on late-init on post-fs + start logd # once everything is setup, no need to modify / mount rootfs rootfs / ro remount # mount shared so changes propagate into child namespaces @@ -485,6 +486,7 @@ service logd /system/bin/logd socket logdw dgram 0222 logd logd service logd-reinit /system/bin/logd --reinit + start logd oneshot disabled |