summaryrefslogtreecommitdiff
path: root/base/errors_unix.cpp
diff options
context:
space:
mode:
authorJiyong Park <jiyong@google.com>2019-05-10 21:12:15 +0900
committerJiyong Park <jiyong@google.com>2019-05-29 07:04:27 +0900
commitd7f7c208daf4d6134b6f6fd665fdb47993fd980a (patch)
tree47a84207bde0b6fa32c79276d0a6e66ebc9c3a27 /base/errors_unix.cpp
parent2dca1885039ae9e8f55b7828a503396e6002a1cb (diff)
Don't use apexd when TARGET_FLATTEN_APEX == true
When TARGET_FLATTEN_APEX is true (= ro.apex.updatable is unset or set to false), apexd is not used to activate the built-in flattened APEXes. Init simply bind-mounts /system/apex to /apex. However, there is a special case here. The runtime APEX is installed as either /system/apex/com.android.runtime.debug or /system/apex/com.android.runtime.release, whereas it should be activated on /apex/com.android.runtime - without the .debug or .release suffix. To handle that case, the build system creates an empty directory /system/apex/com.android.runtime and the .debug or .release directory is bind-mounted to the empty directory by init at runtime. This change also fixes a minor bug that native watchdog is triggered for all post-apexd processes regardless of whether ro.apex.updatable is true or not. Since apexd is expected to shutdown itself when ro.apex .updatable is false, we don't trigger the watchdog in that case. Bug: 132413565 Bug: 133305381 Test: marlin and sdk_gphone are bootable Merged-In: I219465b8b81decb960e2c5f46bab6e0768b31317 Change-Id: I219465b8b81decb960e2c5f46bab6e0768b31317 (cherry picked from commit f93088ba2bcc77ebbc01924721467455db7a0496)
Diffstat (limited to 'base/errors_unix.cpp')
0 files changed, 0 insertions, 0 deletions