conf: Add detailed explanations for process confs

Sections below needed to be explained more in detail:
 * In the 7.1 section:
    - ActionOnFailure (What it does)
    - OomScore (What are the predefined oom_score_adj values)
 * In the 8.1 section:
    - ACTION_ON_FAILURE (What it does)

Change-Id: I88a892586accec682a6be883e8ef16d31e0acebf
Signed-off-by: SangYoun Kwak <sy.kwak@samsung.com>

diff --git a/conf/README b/conf/README
index c61c470..95443db 100644 (file)
--- a/conf/README
+++ b/conf/README
@@ -550,6 +550,9 @@ Key: ActionOnFailure
 Value: <action>
 Comment: Specify an action on failure.
          <action> can be: reboot
+         If <action> is reboot, then this app|service|process will be added to the watchdog.
+                 If this app|service|process was killed, then the system will reboot.
+         It does same thing as ActionOnFailure in the Private|VIP_GROUP section of vip-process.conf.d.
 Example: ActionOnFailure=reboot
 
 Key: WatchdogAction
@@ -560,11 +563,17 @@ Example: WatchdogAction=ignore
 
 Key: OomScore
 Value: <oom_score_adj>
-Comment: Specify the oom_score_adj.
+Comment: Specify the fixed oom_score_adj.
          oom_score_adj is an integer value between -900 to 250.
          Predefined values cannot be used.
-         Predefined values are: -900, 0, 100, 150, 200, 230, 250
-         (Please refer to procfs.h)
+         Predefined values:
+                 -900 : The lowest oom score value in resourced.
+                 0    : Initial value for services and processes.
+                 100  : Initial value for apps.
+                 150  : Foreground status when it is cpu-locked(prevents sleep).
+                 200  : Foreground status when it is cpu-unlocked(sleep available).
+                 230  : Perceptible apps (background)
+                 250  : Background status when it is cpu-locked(prevents sleep).
 Example: OomScore=125
 
 8. vip-process.d/*.conf
@@ -583,4 +592,7 @@ Key: ACTION_ON_FAILURE
 Value: <action>
 Comment: Specify an action on failure.
          <action> can be: reboot
+         If <action> is reboot, then this app|service|process will be added to the watchdog.
+                 If this app|service|process was killed, then the system will reboot.
+         It does same thing as ActionOnFailure in the Private section of process.conf.d.
 Example: ACTION_ON_FAILURE=reboot