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

diff --git a/src/vconf-buxton-restore-mem-layer.sh b/src/vconf-buxton-restore-mem-layer.sh
index 389225a..3c92171 100755 (executable)
--- a/src/vconf-buxton-restore-mem-layer.sh
+++ b/src/vconf-buxton-restore-mem-layer.sh
@@ -70,7 +70,15 @@ sed 's:^found key ::' |
 while read keydb
 do
     keymem=${keydb#memory_init/}
-    if ! q=$(buxtonctl -s get "$layerdb" "$groupdb" "$keydb")
+    if t=$(buxtonctl -s get "$layermem" "$groupmem" "$keymem")
+    then
+        value=$(echo -n "$t" | sed 's/.* = [^:]*: \(.*\)/\1/')
+        echo "${reset}$keymem is already set as $value"
+        if ! buxtonctl -s set-label "$layermem" "$groupmem" "$keymem" "$label"
+        then
+            echo "${red}ERROR WHILE SETTING LABEL${reset}"
+        fi
+    elif ! q=$(buxtonctl -s get "$layerdb" "$groupdb" "$keydb")
     then
         echo "${red}ERROR can't get value of $keydb${reset}"
     else