Commit 124ff15b authored Apr 07, 2015 by Mark Salyzyn

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

parent bf403968

rootdir/init.rc

+2 −0

Original line number	Diff line number	Diff line
		@@ -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