projects / platform / core / appfw / vconf-buxton.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8374740) | patch
vconf-buxton: Do not restore mem keys what is already set 11/35811/2
authorJiyoung Yun <jy910.yun@samsung.com>
Tue, 24 Feb 2015 10:28:47 +0000 (19:28 +0900)
committerJiyoung Yun <jy910.yun@samsung.com>
Wed, 25 Feb 2015 05:26:27 +0000 (14:26 +0900)
commit7af36e1e5eff1125ecbb0326a33a25f8b24287f5
tree44d60db2e5396d557c8af6815095e50635aa74fctree | snapshot
parent837474017fea13e4c2aa5126666947ff5caa578fcommit | diff
vconf-buxton: Do not restore mem keys what is already set

In booting time, some module who is launched before vconf-setup.service
sometimes set the memory key but it is reset by restore-mem-layer.sh file
when vconf-setup.service is lauched.
This patch does not update mem keys if the keys already have data.

Signed-off-by: Jiyoung Yun <jy910.yun@samsung.com>
Change-Id: I2b24af4ad937a8735104f08d88f62caa491d9c96
src/vconf-buxton-restore-mem-layer.sh diff | blob | history
Domain: App Framework / Configuration;