aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMark Salyzyn2016-03-09 16:58:16 -0600
committerMark Salyzyn2016-03-28 13:07:00 -0500
commita4f701af93a5a739f34823cde0c493dfbc63537a (patch)
treeeff3803e6756b19290d2f9c5277262227b5892f0 /recovery-refresh.rc
parent2dbd06c7ed9e753439fb2c0e17d11ca6323e5157 (diff)
downloadplatform-bootable-recovery-a4f701af93a5a739f34823cde0c493dfbc63537a.tar.gz
platform-bootable-recovery-a4f701af93a5a739f34823cde0c493dfbc63537a.tar.xz
platform-bootable-recovery-a4f701af93a5a739f34823cde0c493dfbc63537a.zip
recovery: use __android_log_pmsg_file_write for log files
- Add call to __android_log_pmsg_file_write for recovery logging. - Add call to refresh pmsg if we reboot back into recovery and then allow overwrite of those logs. - Add a new one-time executable recovery-refresh that refreshes pmsg in post-fs phase of init. We rely on pmsg eventually scrolling off to age the content after recovery-persist has done its job. - Add a new one-time executable recovery-persist that transfers from pmsg to /data/misc/recovery/ directory if /cache is not mounted in post-fs-data phase of init. - Build and appropriately trigger the above two as required if BOARD_CACHEIMAGE_PARTITION_SIZE is undefined. - Add some simple unit tests NB: Test failure is expected on systems that do not deliver either the recovery-persist or recovery-refresh executables, e.g. systems with /cache. Tests also require a timely reboot sequence of test to truly verify, tests provide guidance on stderr to direct. Bug: 27176738 Change-Id: I17bb95980234984f6b2087fd5941b0a3126b706b
Diffstat (limited to 'recovery-refresh.rc')
-rw-r--r--recovery-refresh.rc2
1 files changed, 2 insertions, 0 deletions
diff --git a/recovery-refresh.rc b/recovery-refresh.rc
new file mode 100644
index 00000000..14b05cca
--- /dev/null
+++ b/recovery-refresh.rc
@@ -0,0 +1,2 @@
1on post-fs
2 exec - system log -- /system/bin/recovery-refresh